Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0329e9e9b676550e547baa759df72fad96b8bea7bf75bb3495b7e857934f934c

Tx prefix hash: ccf8a0b07aed0d99d55ea42a78b5dbf2156c833da794889c4030686472b99bf8
Tx public key: a8615300b93ec2b2a09abbf8b90d9fcce7c5751fdeb9b9fe2b3cdb0212c42e45
Timestamp: 1718890413 Timestamp [UCT]: 2024-06-20 13:33:33 Age [y:d:h:m:s]: 00:329:08:28:12
Block: 1048358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235373 RingCT/type: yes/0
Extra: 01a8615300b93ec2b2a09abbf8b90d9fcce7c5751fdeb9b9fe2b3cdb0212c42e450211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9243e8e37bdabf5431afe757e5250c21baa1448b66e1b95143c9dfa80d2dcae 0.600000000000 1518423 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": 1048368, "vin": [ { "gen": { "height": 1048358 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9243e8e37bdabf5431afe757e5250c21baa1448b66e1b95143c9dfa80d2dcae" } } ], "extra": [ 1, 168, 97, 83, 0, 185, 62, 194, 178, 160, 154, 187, 248, 185, 13, 159, 204, 231, 197, 117, 31, 222, 185, 185, 254, 43, 60, 219, 2, 18, 196, 46, 69, 2, 17, 0, 0, 0, 6, 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