Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f72f78e80b53db9eca7fe8d52d7e372bda4289887f2614a26639464e4ce1d9b4

Tx prefix hash: 7c9db96526268c3783e41a61ced3c30c2ff50806290fce51ea7b01488b3094da
Tx public key: 909d8de2f534e4cd4a6c49af3e28eb344d5dbcb4dc96fac29237fce631bed9f5
Timestamp: 1714055458 Timestamp [UCT]: 2024-04-25 14:30:58 Age [y:d:h:m:s]: 01:003:10:50:06
Block: 1008269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263414 RingCT/type: yes/0
Extra: 01909d8de2f534e4cd4a6c49af3e28eb344d5dbcb4dc96fac29237fce631bed9f50211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9242ccfbbaa75f7558d5e9550f3ee5b0b0831fffe4b66a842544723b6981198 0.600000000000 1469737 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": 1008279, "vin": [ { "gen": { "height": 1008269 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9242ccfbbaa75f7558d5e9550f3ee5b0b0831fffe4b66a842544723b6981198" } } ], "extra": [ 1, 144, 157, 141, 226, 245, 52, 228, 205, 74, 108, 73, 175, 62, 40, 235, 52, 77, 93, 188, 180, 220, 150, 250, 194, 146, 55, 252, 230, 49, 190, 217, 245, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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