Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 396735838e35cdb4c064c8276867f2a84181c7ee32ded5f68e74c9318bdb9655

Tx prefix hash: e7f0e4374c15cbb3941db9ed6bffa7233f60862841d4a76d249ddd328279f695
Tx public key: 5746cd0d90d66ec985cab1b5f221aac0be18654e804ea9e0646bf7f963f688dc
Timestamp: 1703295695 Timestamp [UCT]: 2023-12-23 01:41:35 Age [y:d:h:m:s]: 01:323:23:02:15
Block: 919066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 490380 RingCT/type: yes/0
Extra: 015746cd0d90d66ec985cab1b5f221aac0be18654e804ea9e0646bf7f963f688dc02110000001052d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5aab3bba6f1dc36c487f35e2cf66df4fb3ee552acaf7e446f1924477ba77ab62 0.600000000000 1376730 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": 919076, "vin": [ { "gen": { "height": 919066 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5aab3bba6f1dc36c487f35e2cf66df4fb3ee552acaf7e446f1924477ba77ab62" } } ], "extra": [ 1, 87, 70, 205, 13, 144, 214, 110, 201, 133, 202, 177, 181, 242, 33, 170, 192, 190, 24, 101, 78, 128, 78, 169, 224, 100, 107, 247, 249, 99, 246, 136, 220, 2, 17, 0, 0, 0, 16, 82, 212, 126, 148, 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