Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c4eff4dd0d23c11f512a23b0d676b226cd81348b40b0e5a29132bbbe2cb57c5

Tx prefix hash: 14c0057f096f1626f0bba864c31921288c4784f6e86222b86e4fc37a2489e133
Tx public key: 617d27f387f2bb08d75dc0e3c6fd3de90a35272797e1f44de12184c3d18404a4
Timestamp: 1649038566 Timestamp [UCT]: 2022-04-04 02:16:06 Age [y:d:h:m:s]: 03:045:05:57:27
Block: 472700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 812779 RingCT/type: yes/0
Extra: 01617d27f387f2bb08d75dc0e3c6fd3de90a35272797e1f44de12184c3d18404a4021100000005bf7ee4e7000000000000000000

1 output(s) for total of 16.662835943000 dcy

stealth address amount amount idx
00: 44b0a7bd8df6c033314d76c90eb12bbb31f9b46edcce7460d9f78f7c3af7f657 16.662835943000 892363 of 0

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": 472710, "vin": [ { "gen": { "height": 472700 } } ], "vout": [ { "amount": 16662835943, "target": { "key": "44b0a7bd8df6c033314d76c90eb12bbb31f9b46edcce7460d9f78f7c3af7f657" } } ], "extra": [ 1, 97, 125, 39, 243, 135, 242, 187, 8, 215, 93, 192, 227, 198, 253, 61, 233, 10, 53, 39, 39, 151, 225, 244, 77, 225, 33, 132, 195, 209, 132, 4, 164, 2, 17, 0, 0, 0, 5, 191, 126, 228, 231, 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