Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07a79987cdebd32262e7b8e7fb2d89b26554f8a6120c145e04d4288c484771e3

Tx prefix hash: 165d058e60175cde1dde5c953d321a5cac55814b0133ceca05a246aeee695151
Tx public key: b6131157ce6a513513aa3c44e39e3c3749e8f389b7d59155f3779c61fc94aa7e
Timestamp: 1729520966 Timestamp [UCT]: 2024-10-21 14:29:26 Age [y:d:h:m:s]: 01:030:08:03:51
Block: 1136446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280088 RingCT/type: yes/0
Extra: 01b6131157ce6a513513aa3c44e39e3c3749e8f389b7d59155f3779c61fc94aa7e021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 049944915d0c61935bdfbbcc2d4a8c60b34454689e8a7c6c5791c3b07b85695c 0.600000000000 1619791 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": 1136456, "vin": [ { "gen": { "height": 1136446 } } ], "vout": [ { "amount": 600000000, "target": { "key": "049944915d0c61935bdfbbcc2d4a8c60b34454689e8a7c6c5791c3b07b85695c" } } ], "extra": [ 1, 182, 19, 17, 87, 206, 106, 81, 53, 19, 170, 60, 68, 227, 158, 60, 55, 73, 232, 243, 137, 183, 213, 145, 85, 243, 119, 156, 97, 252, 148, 170, 126, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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