Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35d1b74bce4607e48eae586fe30e8c8d5282d17a2060cf61622961b9d5051d6b

Tx prefix hash: b2bb5349f9fdf6792412d5da777f3fad092929c0bf1603929f324f49b6ca8d3b
Tx public key: 9d7913139abbbb332077e92a3f6c9b09afcef421156c489cce1be0153d816ee3
Timestamp: 1722202374 Timestamp [UCT]: 2024-07-28 21:32:54 Age [y:d:h:m:s]: 01:099:20:33:20
Block: 1075808 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329849 RingCT/type: yes/0
Extra: 019d7913139abbbb332077e92a3f6c9b09afcef421156c489cce1be0153d816ee302110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d2f9b8d1109f79d0fc26c49d799dae7808b9205b194d8244e9d6494104563d1 0.600000000000 1548337 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": 1075818, "vin": [ { "gen": { "height": 1075808 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d2f9b8d1109f79d0fc26c49d799dae7808b9205b194d8244e9d6494104563d1" } } ], "extra": [ 1, 157, 121, 19, 19, 154, 187, 187, 51, 32, 119, 233, 42, 63, 108, 155, 9, 175, 206, 244, 33, 21, 108, 72, 156, 206, 27, 224, 21, 61, 129, 110, 227, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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