Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b322bc35dd27d5485c5ef84b1b70f004d194db4cb36417f3faff61b9b6e411b8

Tx prefix hash: a0336e22a51a810cc4cede86964b14f90083c4d8d68318d380778d4a27adc41c
Tx public key: 1f4a2d8e830b4ee34e97ec28f45a19df45f236cff56dd84b6781000ffed54e6b
Timestamp: 1709358788 Timestamp [UCT]: 2024-03-02 05:53:08 Age [y:d:h:m:s]: 01:261:11:57:21
Block: 969341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 445631 RingCT/type: yes/0
Extra: 011f4a2d8e830b4ee34e97ec28f45a19df45f236cff56dd84b6781000ffed54e6b02110000000349a185bb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 168c0b8853fb606fee66838143422e0788b2afb7ae10611abf4f718a81de5117 0.600000000000 1429170 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": 969351, "vin": [ { "gen": { "height": 969341 } } ], "vout": [ { "amount": 600000000, "target": { "key": "168c0b8853fb606fee66838143422e0788b2afb7ae10611abf4f718a81de5117" } } ], "extra": [ 1, 31, 74, 45, 142, 131, 11, 78, 227, 78, 151, 236, 40, 244, 90, 25, 223, 69, 242, 54, 207, 245, 109, 216, 75, 103, 129, 0, 15, 254, 213, 78, 107, 2, 17, 0, 0, 0, 3, 73, 161, 133, 187, 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