Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ae120a6442bd698240f9668416cc95855b2c55a99e3a2b7b3301af24704af90

Tx prefix hash: 1759278de7034d282622c9471221d836a3c533832e7e89ed1a2876d6fed034ff
Tx public key: a914455e68b401660f16b6e7de4911a1424898d53256eeb2f8f14176a7cfb7c3
Timestamp: 1727264725 Timestamp [UCT]: 2024-09-25 11:45:25 Age [y:d:h:m:s]: 01:068:13:32:30
Block: 1117787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307433 RingCT/type: yes/0
Extra: 01a914455e68b401660f16b6e7de4911a1424898d53256eeb2f8f14176a7cfb7c302110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54a326f9f8a0fd7491e183efb5e9716987451a261611eec1d417d3d30d39c4b1 0.600000000000 1598750 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": 1117797, "vin": [ { "gen": { "height": 1117787 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54a326f9f8a0fd7491e183efb5e9716987451a261611eec1d417d3d30d39c4b1" } } ], "extra": [ 1, 169, 20, 69, 94, 104, 180, 1, 102, 15, 22, 182, 231, 222, 73, 17, 161, 66, 72, 152, 213, 50, 86, 238, 178, 248, 241, 65, 118, 167, 207, 183, 195, 2, 17, 0, 0, 0, 1, 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