Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62e15256e4b3541d59abf1b395a2e00bb88aeabf70da1587a6ba3fa436ddf4c6

Tx prefix hash: 5a59526a0fca0da263287446ab16f30ccf3c54543f5e1a0a4031bee6db1dd5c6
Tx public key: 348ce2977837a356b7a6a2ac511fabd5ba83d9e3dbdabf69918f4e08bec3ac6b
Timestamp: 1738949717 Timestamp [UCT]: 2025-02-07 17:35:17 Age [y:d:h:m:s]: 00:285:20:54:52
Block: 1214230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202058 RingCT/type: yes/0
Extra: 01348ce2977837a356b7a6a2ac511fabd5ba83d9e3dbdabf69918f4e08bec3ac6b021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dfb0978ae75dfd12eafc66abe498b4fd2391f1f7c68e259de4259ccea91f7138 0.600000000000 1701017 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": 1214240, "vin": [ { "gen": { "height": 1214230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dfb0978ae75dfd12eafc66abe498b4fd2391f1f7c68e259de4259ccea91f7138" } } ], "extra": [ 1, 52, 140, 226, 151, 120, 55, 163, 86, 183, 166, 162, 172, 81, 31, 171, 213, 186, 131, 217, 227, 219, 218, 191, 105, 145, 143, 78, 8, 190, 195, 172, 107, 2, 17, 0, 0, 0, 5, 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