Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04c3da323ea40a845101c7ef502ff4ab6ebb981e7ecee6a9c845a7675d4caa2d

Tx prefix hash: 5baba4838f54c7ae4a0132573ea56360ceab49fa60a828dbf65b48ef1dfaacc9
Tx public key: 99a29593ca6c9f3b0fb8f14033015bee6d234bd43a28f681b37729a8e8928003
Timestamp: 1729638057 Timestamp [UCT]: 2024-10-22 23:00:57 Age [y:d:h:m:s]: 00:212:17:28:10
Block: 1137427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151875 RingCT/type: yes/0
Extra: 0199a29593ca6c9f3b0fb8f14033015bee6d234bd43a28f681b37729a8e89280030211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 795bdcc60a65a1dd6fc5deddc4a45b65f713d000eb36b9e47b0dfc7385f45ebb 0.600000000000 1620916 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": 1137437, "vin": [ { "gen": { "height": 1137427 } } ], "vout": [ { "amount": 600000000, "target": { "key": "795bdcc60a65a1dd6fc5deddc4a45b65f713d000eb36b9e47b0dfc7385f45ebb" } } ], "extra": [ 1, 153, 162, 149, 147, 202, 108, 159, 59, 15, 184, 241, 64, 51, 1, 91, 238, 109, 35, 75, 212, 58, 40, 246, 129, 179, 119, 41, 168, 232, 146, 128, 3, 2, 17, 0, 0, 0, 1, 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