Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a002355b8103bdc1dc473a5c13526b79b2b5e30e957f4354845e270fce1bf28

Tx prefix hash: f798092553236d76f32e3e7c15dd3a7623855397772f7f40f148163963557bd1
Tx public key: 6e4ac4f6950adc6d5ca4dd69013ecdf5ceb2ba7d8403835db7e9a26108e0edc3
Timestamp: 1727626723 Timestamp [UCT]: 2024-09-29 16:18:43 Age [y:d:h:m:s]: 00:056:03:19:10
Block: 1120784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40122 RingCT/type: yes/0
Extra: 016e4ac4f6950adc6d5ca4dd69013ecdf5ceb2ba7d8403835db7e9a26108e0edc302110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8ff81832d71e7f8bfcdb67a8e18482357698d8231d6901071765dce71ff7fa3 0.600000000000 1602825 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": 1120794, "vin": [ { "gen": { "height": 1120784 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8ff81832d71e7f8bfcdb67a8e18482357698d8231d6901071765dce71ff7fa3" } } ], "extra": [ 1, 110, 74, 196, 246, 149, 10, 220, 109, 92, 164, 221, 105, 1, 62, 205, 245, 206, 178, 186, 125, 132, 3, 131, 93, 183, 233, 162, 97, 8, 224, 237, 195, 2, 17, 0, 0, 0, 9, 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