Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb4dc43dc76e74654f264a3669a9d29efe2829f21dff0ff570396c7885bad8fb

Tx prefix hash: a9eae7f736d5bc12c7954ade0fe7f4aca6c43314e8bc67bbc5243f0b8dd4f3a1
Tx public key: 0dd6a00f098c449e7757ed849d2916a9731afdf21407b5167a0d74ca4a3525f3
Timestamp: 1719006154 Timestamp [UCT]: 2024-06-21 21:42:34 Age [y:d:h:m:s]: 00:268:14:45:48
Block: 1049298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191971 RingCT/type: yes/0
Extra: 010dd6a00f098c449e7757ed849d2916a9731afdf21407b5167a0d74ca4a3525f302110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8412beed6698f610f2041585f2aa0f3098f17804749c5b5f853dce180a889392 0.600000000000 1519397 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": 1049308, "vin": [ { "gen": { "height": 1049298 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8412beed6698f610f2041585f2aa0f3098f17804749c5b5f853dce180a889392" } } ], "extra": [ 1, 13, 214, 160, 15, 9, 140, 68, 158, 119, 87, 237, 132, 157, 41, 22, 169, 115, 26, 253, 242, 20, 7, 181, 22, 122, 13, 116, 202, 74, 53, 37, 243, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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