Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 776ba1655f266a93fb4d894b529fc28c5ba4cb645a1c41875af586235e41add5

Tx prefix hash: de67ab4b6aac30fbee0a0b829894e7e9756cdb8352a2704eb25d6a889dcf7939
Tx public key: 89110f79cb105c2df92b10ac0d98bbd26c16d3e0816bd183fb683cc58b69a026
Timestamp: 1705231736 Timestamp [UCT]: 2024-01-14 11:28:56 Age [y:d:h:m:s]: 01:124:13:19:08
Block: 935114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350143 RingCT/type: yes/0
Extra: 0189110f79cb105c2df92b10ac0d98bbd26c16d3e0816bd183fb683cc58b69a02602110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 911a48ebd885447f75ddfe1b4a8cd1f1bc4db05ce2bbe6ad733337f57c6667b3 0.600000000000 1393130 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": 935124, "vin": [ { "gen": { "height": 935114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "911a48ebd885447f75ddfe1b4a8cd1f1bc4db05ce2bbe6ad733337f57c6667b3" } } ], "extra": [ 1, 137, 17, 15, 121, 203, 16, 92, 45, 249, 43, 16, 172, 13, 152, 187, 210, 108, 22, 211, 224, 129, 107, 209, 131, 251, 104, 60, 197, 139, 105, 160, 38, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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