Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e89505ece1037d9b09c22e5d2ea27ab60f3470a99067a0d228b29c5e8cbb6179

Tx prefix hash: 341360f9085a686e1f7105c6b8053810ef4fa6293032ee83b8c1d7ff4e978c1a
Tx public key: 876690f4231d5e71329207fb82c902f9a40968bb46436aeae1e0a4db093ee0b7
Timestamp: 1732124353 Timestamp [UCT]: 2024-11-20 17:39:13 Age [y:d:h:m:s]: 00:135:17:15:50
Block: 1157975 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96817 RingCT/type: yes/0
Extra: 01876690f4231d5e71329207fb82c902f9a40968bb46436aeae1e0a4db093ee0b70211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fbf9782ea3d8bc2d4d0b65cc2d95d55cdb990a04aee1fb5d38aed71f22153346 0.600000000000 1643598 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": 1157985, "vin": [ { "gen": { "height": 1157975 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbf9782ea3d8bc2d4d0b65cc2d95d55cdb990a04aee1fb5d38aed71f22153346" } } ], "extra": [ 1, 135, 102, 144, 244, 35, 29, 94, 113, 50, 146, 7, 251, 130, 201, 2, 249, 164, 9, 104, 187, 70, 67, 106, 234, 225, 224, 164, 219, 9, 62, 224, 183, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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