Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fc1642eefb3fc21b663221b91b8d5d6ef584f1b8465ac535e439ef8f6be474e

Tx prefix hash: e5af18eb93a1ac4e297ad058227561f8106ae13f3efac9cb449ae11ed0be47a2
Tx public key: 5b94b27e028f5ae531cdeb857627fe96f489e20630892863006ecbd0d6734a18
Timestamp: 1720201206 Timestamp [UCT]: 2024-07-05 17:40:06 Age [y:d:h:m:s]: 00:299:13:03:47
Block: 1059218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214037 RingCT/type: yes/0
Extra: 015b94b27e028f5ae531cdeb857627fe96f489e20630892863006ecbd0d6734a180211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 22df1a18c1b94e5970be5066ef1c57e096ca05ea545ae89d8478dbbc3fa4c7d8 0.600000000000 1529685 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": 1059228, "vin": [ { "gen": { "height": 1059218 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22df1a18c1b94e5970be5066ef1c57e096ca05ea545ae89d8478dbbc3fa4c7d8" } } ], "extra": [ 1, 91, 148, 178, 126, 2, 143, 90, 229, 49, 205, 235, 133, 118, 39, 254, 150, 244, 137, 226, 6, 48, 137, 40, 99, 0, 110, 203, 208, 214, 115, 74, 24, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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