Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b7ef325a7f770c5c00fc0fb4c4394d699380c7d934bd481330caa4b4c417c71

Tx prefix hash: 1400cb288ca1ba9c8005ed70b0ab61ee2812051efb6932d92ca4f7129e7cc35d
Tx public key: b287ff4d9cff96bd83ac9ef6b0bf26fa38fcdd6ce6ea689d53a2bb00c2f58b9a
Timestamp: 1702196935 Timestamp [UCT]: 2023-12-10 08:28:55 Age [y:d:h:m:s]: 01:110:04:58:04
Block: 909967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339889 RingCT/type: yes/0
Extra: 01b287ff4d9cff96bd83ac9ef6b0bf26fa38fcdd6ce6ea689d53a2bb00c2f58b9a0211000000054b8f5122000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4553eff06acb63757319b10b19af9cf73c12cd31e87a215cb415a57a49ede43e 0.600000000000 1367104 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": 909977, "vin": [ { "gen": { "height": 909967 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4553eff06acb63757319b10b19af9cf73c12cd31e87a215cb415a57a49ede43e" } } ], "extra": [ 1, 178, 135, 255, 77, 156, 255, 150, 189, 131, 172, 158, 246, 176, 191, 38, 250, 56, 252, 221, 108, 230, 234, 104, 157, 83, 162, 187, 0, 194, 245, 139, 154, 2, 17, 0, 0, 0, 5, 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