Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36fa999e0f944bf85e94e1434fa2b6683f7a600a4b88ca38ec7352a6f0c3c6bd

Tx prefix hash: 3775a33b73e161a5b47d733c378e4aced0c82c1565a6bc345133d8a7a2f80b93
Tx public key: d9e4a312fc4ff5711592a0409737e73a078b79a2ae92635c7762ee14a66b37af
Timestamp: 1719984958 Timestamp [UCT]: 2024-07-03 05:35:58 Age [y:d:h:m:s]: 00:113:15:49:26
Block: 1057429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81380 RingCT/type: yes/0
Extra: 01d9e4a312fc4ff5711592a0409737e73a078b79a2ae92635c7762ee14a66b37af021100000002341001ae000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd40d0559f855c6fae3f13aa88bd5d58cbb5afb6c2efa9464ed69bcb8d669175 0.600000000000 1527864 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": 1057439, "vin": [ { "gen": { "height": 1057429 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd40d0559f855c6fae3f13aa88bd5d58cbb5afb6c2efa9464ed69bcb8d669175" } } ], "extra": [ 1, 217, 228, 163, 18, 252, 79, 245, 113, 21, 146, 160, 64, 151, 55, 231, 58, 7, 139, 121, 162, 174, 146, 99, 92, 119, 98, 238, 20, 166, 107, 55, 175, 2, 17, 0, 0, 0, 2, 52, 16, 1, 174, 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