Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d30e5cf76dc6d785fe96ef7059b61400fd0d5c5c46d30f7e2e046dfbf12c182

Tx prefix hash: dd548a43904c5da967288844e86c38e11364f1cf8c67fc9451ed40c85f311f87
Tx public key: 7ada9900280d9524477560dc5caf4f3aedbf8ccc4cbb9a7d1267ff52bfadcebc
Timestamp: 1700414044 Timestamp [UCT]: 2023-11-19 17:14:04 Age [y:d:h:m:s]: 01:058:11:13:47
Block: 895180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303178 RingCT/type: yes/0
Extra: 017ada9900280d9524477560dc5caf4f3aedbf8ccc4cbb9a7d1267ff52bfadcebc021100000009e6d27f9c000000000000000000

1 output(s) for total of 0.663585738000 dcy

stealth address amount amount idx
00: c01bd294ff60396c801fa4828ebe18a4930457316e43b89c76f3c54bb8e1865f 0.663585738000 1351403 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": 895190, "vin": [ { "gen": { "height": 895180 } } ], "vout": [ { "amount": 663585738, "target": { "key": "c01bd294ff60396c801fa4828ebe18a4930457316e43b89c76f3c54bb8e1865f" } } ], "extra": [ 1, 122, 218, 153, 0, 40, 13, 149, 36, 71, 117, 96, 220, 92, 175, 79, 58, 237, 191, 140, 204, 76, 187, 154, 125, 18, 103, 255, 82, 191, 173, 206, 188, 2, 17, 0, 0, 0, 9, 230, 210, 127, 156, 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