Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb7e6568bfad69c3eb5e7d3d0808d1db93c52186adedf04ee93cf98d6524464d

Tx prefix hash: 24e1b7cc8fde10267654698887b6695b96ea87f48ed25f3b547407afc19da3f8
Tx public key: 12c6185e1a47b6bf41f25bf0ca0e99a2a23cab66b8d3d1d100225cd17802c07a
Timestamp: 1714856554 Timestamp [UCT]: 2024-05-04 21:02:34 Age [y:d:h:m:s]: 00:357:17:37:57
Block: 1014924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255723 RingCT/type: yes/0
Extra: 0112c6185e1a47b6bf41f25bf0ca0e99a2a23cab66b8d3d1d100225cd17802c07a0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6ba3e1e7139768a3a9e01b6f674cc6ae1ac2d984b1ba15dba34cfe6c1598920 0.600000000000 1478147 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": 1014934, "vin": [ { "gen": { "height": 1014924 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6ba3e1e7139768a3a9e01b6f674cc6ae1ac2d984b1ba15dba34cfe6c1598920" } } ], "extra": [ 1, 18, 198, 24, 94, 26, 71, 182, 191, 65, 242, 91, 240, 202, 14, 153, 162, 162, 60, 171, 102, 184, 211, 209, 209, 0, 34, 92, 209, 120, 2, 192, 122, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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