Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81ed02ca552649eb9ffa168389b328e994c5f6d6a9b5cd15e94d474651dcb78c

Tx prefix hash: 795d28d991a06fc51fcd5d7256dabef4345ba86ccc997b12fbf7ea968ce478de
Tx public key: 8bc93565d2db21fd1c9dba942c39eb8307517e1e64f5e8dd4f76f38b74e9403f
Timestamp: 1734777675 Timestamp [UCT]: 2024-12-21 10:41:15 Age [y:d:h:m:s]: 00:014:19:51:28
Block: 1179983 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10585 RingCT/type: yes/0
Extra: 018bc93565d2db21fd1c9dba942c39eb8307517e1e64f5e8dd4f76f38b74e9403f0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72d77785456293996f3dc5179b14a6ece12b7dc705a94212fe129d8f013f908d 0.600000000000 1666386 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": 1179993, "vin": [ { "gen": { "height": 1179983 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72d77785456293996f3dc5179b14a6ece12b7dc705a94212fe129d8f013f908d" } } ], "extra": [ 1, 139, 201, 53, 101, 210, 219, 33, 253, 28, 157, 186, 148, 44, 57, 235, 131, 7, 81, 126, 30, 100, 245, 232, 221, 79, 118, 243, 139, 116, 233, 64, 63, 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