Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7dfca613c3a5e9583d334f36cf67404ff1c944771599cbcc67f5244ffdafd16b

Tx prefix hash: 97af931d960533a57ab827ef2c254f6d11c8b0d0d8b2f0f0c1c7426b8beb7f2e
Tx public key: fc6dcf8ff791d9d620ec1f9f15c6cf0a62106a48ed64c249fd43c5ecc1f883a2
Timestamp: 1726279420 Timestamp [UCT]: 2024-09-14 02:03:40 Age [y:d:h:m:s]: 00:214:20:16:31
Block: 1109616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153383 RingCT/type: yes/0
Extra: 01fc6dcf8ff791d9d620ec1f9f15c6cf0a62106a48ed64c249fd43c5ecc1f883a202110000000ee914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 242b71c8059e941877680544a17596916df806a8bf04097637784b5915b027d4 0.600000000000 1587933 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": 1109626, "vin": [ { "gen": { "height": 1109616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "242b71c8059e941877680544a17596916df806a8bf04097637784b5915b027d4" } } ], "extra": [ 1, 252, 109, 207, 143, 247, 145, 217, 214, 32, 236, 31, 159, 21, 198, 207, 10, 98, 16, 106, 72, 237, 100, 194, 73, 253, 67, 197, 236, 193, 248, 131, 162, 2, 17, 0, 0, 0, 14, 233, 20, 221, 21, 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