Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc4b7d933ea96c4bf6a56a06f25935339849cc2b761e3ba5d9097bd5c334242c

Tx prefix hash: a53dd304ecf47db04e95cb1629be676100d2ae9fc04c02c719893fc7e4a03390
Tx public key: 161f2e501df6346bc87682d246dca0739e72bde17c051f60101fb1d4b18c9905
Timestamp: 1702161111 Timestamp [UCT]: 2023-12-09 22:31:51 Age [y:d:h:m:s]: 01:330:02:05:14
Block: 909668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 494757 RingCT/type: yes/0
Extra: 01161f2e501df6346bc87682d246dca0739e72bde17c051f60101fb1d4b18c99050211000000034b8f5122000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce957b131eb89c69d22f7121eac364549e99a4e99bfc6cba14af31d4250d9b3c 0.600000000000 1366773 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": 909678, "vin": [ { "gen": { "height": 909668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce957b131eb89c69d22f7121eac364549e99a4e99bfc6cba14af31d4250d9b3c" } } ], "extra": [ 1, 22, 31, 46, 80, 29, 246, 52, 107, 200, 118, 130, 210, 70, 220, 160, 115, 158, 114, 189, 225, 124, 5, 31, 96, 16, 31, 177, 212, 177, 140, 153, 5, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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