Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 47361c1875f67ed42638337142259030742a711218b495b6314081907c6a5cc1

Tx prefix hash: 19f8c70cc4cc3f27e48fd49afce58ad3155e271f92e6b10b98477ca003c6356d
Tx public key: e8aac3d7a252b975e5e3021d33cc373c00e52ebabf641066d29ee8aa1fae55ee
Timestamp: 1732171498 Timestamp [UCT]: 2024-11-21 06:44:58 Age [y:d:h:m:s]: 00:115:15:48:30
Block: 1158363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82488 RingCT/type: yes/0
Extra: 01e8aac3d7a252b975e5e3021d33cc373c00e52ebabf641066d29ee8aa1fae55ee021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2373b86f229e4c6451e56e42d5ac3b7c7c8f49b1dd7fc9426f44533cd48cc749 0.600000000000 1643992 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1158373, "vin": [ { "gen": { "height": 1158363 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2373b86f229e4c6451e56e42d5ac3b7c7c8f49b1dd7fc9426f44533cd48cc749" } } ], "extra": [ 1, 232, 170, 195, 215, 162, 82, 185, 117, 229, 227, 2, 29, 51, 204, 55, 60, 0, 229, 46, 186, 191, 100, 16, 102, 210, 158, 232, 170, 31, 174, 85, 238, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8