Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4188a78015d1868801e70cd832585cd611cb520f14ba8d2f48b085bbec04e818

Tx prefix hash: 9d02044cace96b3e0537f758240c0e5d3988cfd50440873f4f0ae0d714ac090a
Tx public key: 9e9e89d3aefa66654b48b84f4371c7ef3634ab57ec6d4937154e37cfd6ebdeb0
Timestamp: 1724304674 Timestamp [UCT]: 2024-08-22 05:31:14 Age [y:d:h:m:s]: 00:280:10:00:30
Block: 1093252 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200317 RingCT/type: yes/0
Extra: 019e9e89d3aefa66654b48b84f4371c7ef3634ab57ec6d4937154e37cfd6ebdeb0021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e3c28e63c4fba61629fe63646e826b0d81c437e3bb8e4a6ee2eb4bf75b38796 0.600000000000 1568161 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": 1093262, "vin": [ { "gen": { "height": 1093252 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e3c28e63c4fba61629fe63646e826b0d81c437e3bb8e4a6ee2eb4bf75b38796" } } ], "extra": [ 1, 158, 158, 137, 211, 174, 250, 102, 101, 75, 72, 184, 79, 67, 113, 199, 239, 54, 52, 171, 87, 236, 109, 73, 55, 21, 78, 55, 207, 214, 235, 222, 176, 2, 17, 0, 0, 0, 6, 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