Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78d53de52d14f4b390e7d2abed3a4846bb9230a26b8457b5d3093578253a705c

Tx prefix hash: 115735a6b90eb38f67eee0781a64810215ad0948a2aecb6af5b8df61f2c6ae8d
Tx public key: 560e009aeb855045fc5a7f4bc58a67e91c7ad1b60d9a15f0bfc96c78010512fa
Timestamp: 1728038867 Timestamp [UCT]: 2024-10-04 10:47:47 Age [y:d:h:m:s]: 00:110:14:16:59
Block: 1124207 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79018 RingCT/type: yes/0
Extra: 01560e009aeb855045fc5a7f4bc58a67e91c7ad1b60d9a15f0bfc96c78010512fa02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b0b9edfd92786020d5d9dc79677825c99a9ad41d009757dda29a45380c0d6e6 0.600000000000 1606798 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": 1124217, "vin": [ { "gen": { "height": 1124207 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b0b9edfd92786020d5d9dc79677825c99a9ad41d009757dda29a45380c0d6e6" } } ], "extra": [ 1, 86, 14, 0, 154, 235, 133, 80, 69, 252, 90, 127, 75, 197, 138, 103, 233, 28, 122, 209, 182, 13, 154, 21, 240, 191, 201, 108, 120, 1, 5, 18, 250, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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