Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 738915976e7232ae91a91c4300fa16f4247113b56454a8c738592b834ae4e50d

Tx prefix hash: 5a6df70d4c246c4c8a4f0d8b8f5010170ab226b506557c42c0b5523ff2cb111c
Tx public key: 6994346e784f95de9e6a74d760b3e5bbb217881f3e8dfd2aa3b690624437a191
Timestamp: 1726428197 Timestamp [UCT]: 2024-09-15 19:23:17 Age [y:d:h:m:s]: 00:186:01:07:38
Block: 1110846 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132808 RingCT/type: yes/0
Extra: 016994346e784f95de9e6a74d760b3e5bbb217881f3e8dfd2aa3b690624437a19102110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d44f4d15caf8789e14e9aa5e1399f2ebf96e60f20457322c120c2c81d84cf0df 0.600000000000 1589599 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": 1110856, "vin": [ { "gen": { "height": 1110846 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d44f4d15caf8789e14e9aa5e1399f2ebf96e60f20457322c120c2c81d84cf0df" } } ], "extra": [ 1, 105, 148, 52, 110, 120, 79, 149, 222, 158, 106, 116, 215, 96, 179, 229, 187, 178, 23, 136, 31, 62, 141, 253, 42, 163, 182, 144, 98, 68, 55, 161, 145, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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