Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b16fda878ca3e9b9bc9f5444c88cbc41f4b9ab4b07873347547a89ee92a071e7

Tx prefix hash: 134df499bbbc373153ba9a13dc3216e0ec8cf68da400c308d9efb9a473990bd9
Tx public key: 4b7ea8033a12d60a61d7875c693bf93adf987d24404abfa8f99c138412c2bdc8
Timestamp: 1706347839 Timestamp [UCT]: 2024-01-27 09:30:39 Age [y:d:h:m:s]: 01:069:21:31:15
Block: 944349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311039 RingCT/type: yes/0
Extra: 014b7ea8033a12d60a61d7875c693bf93adf987d24404abfa8f99c138412c2bdc80211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff69f3918fabdc05a4496fc3d2db450a68f29908c5b47c2b7e1739051392c38f 0.600000000000 1402585 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": 944359, "vin": [ { "gen": { "height": 944349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff69f3918fabdc05a4496fc3d2db450a68f29908c5b47c2b7e1739051392c38f" } } ], "extra": [ 1, 75, 126, 168, 3, 58, 18, 214, 10, 97, 215, 135, 92, 105, 59, 249, 58, 223, 152, 125, 36, 64, 74, 191, 168, 249, 156, 19, 132, 18, 194, 189, 200, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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