Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d2c3e2a3280dc403022e8ea18f703b61c4cbceec6248c01892a27070531a508

Tx prefix hash: 7e6f4a37a9d1b23b4ee21cf3f5e2c74fbecdf98b9d6847b44c8210c9adc4b1e6
Tx public key: 79a474be53182b107e1b6956479e4e62d9b49c86efdefd9f44f89f860511a6c3
Timestamp: 1725574953 Timestamp [UCT]: 2024-09-05 22:22:33 Age [y:d:h:m:s]: 00:209:09:59:58
Block: 1103781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149501 RingCT/type: yes/0
Extra: 0179a474be53182b107e1b6956479e4e62d9b49c86efdefd9f44f89f860511a6c3021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 542ca491364d8e52c7b93a30a85a68a4b9e6ee9aaf1abb72f136b3fffb27630b 0.600000000000 1580742 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": 1103791, "vin": [ { "gen": { "height": 1103781 } } ], "vout": [ { "amount": 600000000, "target": { "key": "542ca491364d8e52c7b93a30a85a68a4b9e6ee9aaf1abb72f136b3fffb27630b" } } ], "extra": [ 1, 121, 164, 116, 190, 83, 24, 43, 16, 126, 27, 105, 86, 71, 158, 78, 98, 217, 180, 156, 134, 239, 222, 253, 159, 68, 248, 159, 134, 5, 17, 166, 195, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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