Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 855acb227532dd8a9b199e28b4aa17acb92d68d680ef6dcc72d2c0f0634dfa8a

Tx prefix hash: 88270c044f1a49e488cfac7e9c096ff04e313784c84d6a97c97422f2fbd83718
Tx public key: ef229ff4a36adf3d28afb3d1bef3244a8085e4039c782c6c9815de15b1aceb35
Timestamp: 1736969525 Timestamp [UCT]: 2025-01-15 19:32:05 Age [y:d:h:m:s]: 00:335:19:55:32
Block: 1198088 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237571 RingCT/type: yes/0
Extra: 01ef229ff4a36adf3d28afb3d1bef3244a8085e4039c782c6c9815de15b1aceb350211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b4334505a4004e12a5d490020546d212e80c3be1bcb6fc9d6c8fcbde2489232 0.600000000000 1684707 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": 1198098, "vin": [ { "gen": { "height": 1198088 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b4334505a4004e12a5d490020546d212e80c3be1bcb6fc9d6c8fcbde2489232" } } ], "extra": [ 1, 239, 34, 159, 244, 163, 106, 223, 61, 40, 175, 179, 209, 190, 243, 36, 74, 128, 133, 228, 3, 156, 120, 44, 108, 152, 21, 222, 21, 177, 172, 235, 53, 2, 17, 0, 0, 0, 5, 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