Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d43092ee612254ea884914f35831d73a5d5242ff25bd681ad1b6f5a68751e2a

Tx prefix hash: 53d9b5e5b562d53857a37a9ce87aa3e4d909ed8fb6a00a048a9c7f93084231ab
Tx public key: 6df1699e108798354c98f96c10bf099a2487a2419fa4082e84f79b0468ce4fb6
Timestamp: 1722363701 Timestamp [UCT]: 2024-07-30 18:21:41 Age [y:d:h:m:s]: 00:261:19:07:08
Block: 1077148 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187025 RingCT/type: yes/0
Extra: 016df1699e108798354c98f96c10bf099a2487a2419fa4082e84f79b0468ce4fb602110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9906ba01d11e41dd66dc408826ed6ccff0fa837fc35c46d3a597744da58ee4ea 0.600000000000 1549693 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": 1077158, "vin": [ { "gen": { "height": 1077148 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9906ba01d11e41dd66dc408826ed6ccff0fa837fc35c46d3a597744da58ee4ea" } } ], "extra": [ 1, 109, 241, 105, 158, 16, 135, 152, 53, 76, 152, 249, 108, 16, 191, 9, 154, 36, 135, 162, 65, 159, 164, 8, 46, 132, 247, 155, 4, 104, 206, 79, 182, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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