Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f68091eb5505b783b88a45cd202982811ab46b61104372fc651f46fea45a295e

Tx prefix hash: ea7a2fc36a0c32f3d8ed5890ab5197b4dcf95745c682768a1a28d7b9a8040b1c
Tx public key: ce9ea0cec60acc1f2d61339c88c4bf8296585096eefb015be56f4f97f53aa736
Timestamp: 1683528140 Timestamp [UCT]: 2023-05-08 06:42:20 Age [y:d:h:m:s]: 01:261:06:27:33
Block: 755444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 448142 RingCT/type: yes/0
Extra: 01ce9ea0cec60acc1f2d61339c88c4bf8296585096eefb015be56f4f97f53aa736021100000002b3164c24000000000000000000

1 output(s) for total of 1.927083902000 dcy

stealth address amount amount idx
00: 8479db4b14f04cf2e8f14bb5cf61f26fbac4e84218ae0076d0a38204c50a4ae2 1.927083902000 1203759 of 0

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": 755454, "vin": [ { "gen": { "height": 755444 } } ], "vout": [ { "amount": 1927083902, "target": { "key": "8479db4b14f04cf2e8f14bb5cf61f26fbac4e84218ae0076d0a38204c50a4ae2" } } ], "extra": [ 1, 206, 158, 160, 206, 198, 10, 204, 31, 45, 97, 51, 156, 136, 196, 191, 130, 150, 88, 80, 150, 238, 251, 1, 91, 229, 111, 79, 151, 245, 58, 167, 54, 2, 17, 0, 0, 0, 2, 179, 22, 76, 36, 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