Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f603a57132e3debe9ac75bf92ee39a488a0de24a3cc4519845393ffef059651

Tx prefix hash: 7ba063ac522eafccebf40a77c630e394c4cce7c51beb4aa0ccc93c2cea185651
Tx public key: f735d9092f82c4e283f0e7c0fcad50e596b97b3a3247aed466eb61ef35a2323b
Timestamp: 1709519571 Timestamp [UCT]: 2024-03-04 02:32:51 Age [y:d:h:m:s]: 01:065:21:25:34
Block: 970675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308106 RingCT/type: yes/0
Extra: 01f735d9092f82c4e283f0e7c0fcad50e596b97b3a3247aed466eb61ef35a2323b02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05761d00bedf584ce85df696f0d111ebf29d30255c21a956e8a0e0d2b25b3cf2 0.600000000000 1430534 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": 970685, "vin": [ { "gen": { "height": 970675 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05761d00bedf584ce85df696f0d111ebf29d30255c21a956e8a0e0d2b25b3cf2" } } ], "extra": [ 1, 247, 53, 217, 9, 47, 130, 196, 226, 131, 240, 231, 192, 252, 173, 80, 229, 150, 185, 123, 58, 50, 71, 174, 212, 102, 235, 97, 239, 53, 162, 50, 59, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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