Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e292b95e537584ba8869a0ec64bbb27fc47b902c1ea70644a9d9ac4c646cc2c

Tx prefix hash: a37ebaa638ff1463fa74f43cf5f90994cff47343e4f6b25c5ceb263099862282
Tx public key: 1f9e355574aa22ed7ea737dfe2512208ea9f8af6aec595a407f08040de4bd20a
Timestamp: 1703972816 Timestamp [UCT]: 2023-12-30 21:46:56 Age [y:d:h:m:s]: 01:106:02:18:56
Block: 924672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336945 RingCT/type: yes/0
Extra: 011f9e355574aa22ed7ea737dfe2512208ea9f8af6aec595a407f08040de4bd20a0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1142887f0cdb51baa0279633d99177598287cb80d0f474fa8cf4f384af2b9602 0.600000000000 1382428 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": 924682, "vin": [ { "gen": { "height": 924672 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1142887f0cdb51baa0279633d99177598287cb80d0f474fa8cf4f384af2b9602" } } ], "extra": [ 1, 31, 158, 53, 85, 116, 170, 34, 237, 126, 167, 55, 223, 226, 81, 34, 8, 234, 159, 138, 246, 174, 197, 149, 164, 7, 240, 128, 64, 222, 75, 210, 10, 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