Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71e86e213389125b518d3d84734dd7ad78dceed8eb1e038b5cf7d3221cfd46c9

Tx prefix hash: 722b5f964b1e2457e5dd05f09f3fde23d06bfe68c7b948a2bbd68f0d5fd18e71
Tx public key: 862f2d0edfa578e17a550f884d27f2e864db9f5710afac6986a15ef5e0ea9f33
Timestamp: 1720928040 Timestamp [UCT]: 2024-07-14 03:34:00 Age [y:d:h:m:s]: 00:290:00:30:05
Block: 1065262 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207215 RingCT/type: yes/0
Extra: 01862f2d0edfa578e17a550f884d27f2e864db9f5710afac6986a15ef5e0ea9f33021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b517c22d721dcaf4ad4cb2f48447f4df38e88aff28e46760cd3cedf40a6eb5d 0.600000000000 1535807 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": 1065272, "vin": [ { "gen": { "height": 1065262 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b517c22d721dcaf4ad4cb2f48447f4df38e88aff28e46760cd3cedf40a6eb5d" } } ], "extra": [ 1, 134, 47, 45, 14, 223, 165, 120, 225, 122, 85, 15, 136, 77, 39, 242, 232, 100, 219, 159, 87, 16, 175, 172, 105, 134, 161, 94, 245, 224, 234, 159, 51, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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