Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf417427e38639acb948b7567aa8ce885d75f04d861eab2bd6c9e43f16b206b9

Tx prefix hash: e448a95c2cf1735dab42c8fadd115476e20fd1c35c837e67fd778ed62bcff940
Tx public key: 2bd531a10ac5e73a86c8761f34f194a2ff70de4070df367c3a93318560859c6d
Timestamp: 1734843142 Timestamp [UCT]: 2024-12-22 04:52:22 Age [y:d:h:m:s]: 00:094:07:29:14
Block: 1180528 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67144 RingCT/type: yes/0
Extra: 012bd531a10ac5e73a86c8761f34f194a2ff70de4070df367c3a93318560859c6d02110000000d1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e6c9fa9fad1b174d6fd374afb07f760eb1defaf2381244cf362283c04d0c6ea 0.600000000000 1666941 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": 1180538, "vin": [ { "gen": { "height": 1180528 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e6c9fa9fad1b174d6fd374afb07f760eb1defaf2381244cf362283c04d0c6ea" } } ], "extra": [ 1, 43, 213, 49, 161, 10, 197, 231, 58, 134, 200, 118, 31, 52, 241, 148, 162, 255, 112, 222, 64, 112, 223, 54, 124, 58, 147, 49, 133, 96, 133, 156, 109, 2, 17, 0, 0, 0, 13, 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