Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0be5698b67d634fa685979ce77bf53f3450df0e00e9c3a9b7bd441fa10148ed8

Tx prefix hash: 6808bca21b2b38a782ef80b3d592d6ecaf3d3352d3728a1d66e940d1b74200f4
Tx public key: 2dfc8b5e53e57e185976cb83e68b60b27a83e3fea576fac1cc01160520afdd8b
Timestamp: 1737414403 Timestamp [UCT]: 2025-01-20 23:06:43 Age [y:d:h:m:s]: 00:148:01:44:24
Block: 1201736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105566 RingCT/type: yes/0
Extra: 012dfc8b5e53e57e185976cb83e68b60b27a83e3fea576fac1cc01160520afdd8b021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a948ae28a09ff1fa6e35cde0c9015029df17652e5a18def8a1444e943e78ce3 0.600000000000 1688393 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": 1201746, "vin": [ { "gen": { "height": 1201736 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a948ae28a09ff1fa6e35cde0c9015029df17652e5a18def8a1444e943e78ce3" } } ], "extra": [ 1, 45, 252, 139, 94, 83, 229, 126, 24, 89, 118, 203, 131, 230, 139, 96, 178, 122, 131, 227, 254, 165, 118, 250, 193, 204, 1, 22, 5, 32, 175, 221, 139, 2, 17, 0, 0, 0, 5, 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