Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cbb3f482df9fce711fb991529c53f491189e5bd417a771d4416ae5c64449121

Tx prefix hash: 3da1b9a7cce35a7eba5ebf72d2c920814be4dd18b7067475caa69f9224ae7484
Tx public key: 97574dca1ea8dc0d02d837c7e0daa0ed24b6d03055005900587a5f24c2195fa7
Timestamp: 1734310832 Timestamp [UCT]: 2024-12-16 01:00:32 Age [y:d:h:m:s]: 00:099:20:18:52
Block: 1176111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71122 RingCT/type: yes/0
Extra: 0197574dca1ea8dc0d02d837c7e0daa0ed24b6d03055005900587a5f24c2195fa7021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca8737bb618c6f3a927eb2c308e73b7c1d2d8210d1bedf5298528896514c3254 0.600000000000 1662442 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": 1176121, "vin": [ { "gen": { "height": 1176111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca8737bb618c6f3a927eb2c308e73b7c1d2d8210d1bedf5298528896514c3254" } } ], "extra": [ 1, 151, 87, 77, 202, 30, 168, 220, 13, 2, 216, 55, 199, 224, 218, 160, 237, 36, 182, 208, 48, 85, 0, 89, 0, 88, 122, 95, 36, 194, 25, 95, 167, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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