Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8978f34ae72505f1a0a753ad8d2e4c987c0d10773bb944e82ccb884131793180

Tx prefix hash: 31a95b2c08cf49f301b189afdf4732ba75404e05a51963197b5f3e230a0e81ae
Tx public key: a7e5bb724e2fb23f6b248a51ff8944777b6183b9233e8bd38cb34df6502fd0a7
Timestamp: 1737241239 Timestamp [UCT]: 2025-01-18 23:00:39 Age [y:d:h:m:s]: 00:151:07:14:43
Block: 1200310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107844 RingCT/type: yes/0
Extra: 01a7e5bb724e2fb23f6b248a51ff8944777b6183b9233e8bd38cb34df6502fd0a70211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7ce9b184259551eb9962c9d5a0ba23a6833fac1ee7074eb8fdcbc184af19e6e 0.600000000000 1686953 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": 1200320, "vin": [ { "gen": { "height": 1200310 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7ce9b184259551eb9962c9d5a0ba23a6833fac1ee7074eb8fdcbc184af19e6e" } } ], "extra": [ 1, 167, 229, 187, 114, 78, 47, 178, 63, 107, 36, 138, 81, 255, 137, 68, 119, 123, 97, 131, 185, 35, 62, 139, 211, 140, 179, 77, 246, 80, 47, 208, 167, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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