Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de4bf03ac99b6aeaa3096811c63b99c2d875a4b290f4a264e008c7277f22a844

Tx prefix hash: c66db856e0d926629ed18c7a08c65227c266da0b4859b65ebed7a841fd608865
Tx public key: 5086eed0bacc6c5a09c01c961157d8cde5542195ba928ea6ce9de229902d8c95
Timestamp: 1703605435 Timestamp [UCT]: 2023-12-26 15:43:55 Age [y:d:h:m:s]: 01:317:16:13:45
Block: 921635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485880 RingCT/type: yes/0
Extra: 015086eed0bacc6c5a09c01c961157d8cde5542195ba928ea6ce9de229902d8c950211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd18c7b763c553f033ec50e521c773d1420776431a5556d0c1d611e6bb261235 0.600000000000 1379325 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": 921645, "vin": [ { "gen": { "height": 921635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd18c7b763c553f033ec50e521c773d1420776431a5556d0c1d611e6bb261235" } } ], "extra": [ 1, 80, 134, 238, 208, 186, 204, 108, 90, 9, 192, 28, 150, 17, 87, 216, 205, 229, 84, 33, 149, 186, 146, 142, 166, 206, 157, 226, 41, 144, 45, 140, 149, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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