Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9f5b1335bd0b07afe0cacfacb7e5185b637790f34db9d6b5932c6bdb383da0a

Tx prefix hash: 9a5295950d1fe4f9125509342a84aef8b729033a33b435afd830bc87c5df2dd2
Tx public key: 92a8ac81ef9ce8644bdff8dbc64a16fecb10dd2f52e61d4ed6080efb8af50b86
Timestamp: 1676268289 Timestamp [UCT]: 2023-02-13 06:04:49 Age [y:d:h:m:s]: 01:337:00:16:24
Block: 695889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 501816 RingCT/type: yes/0
Extra: 0192a8ac81ef9ce8644bdff8dbc64a16fecb10dd2f52e61d4ed6080efb8af50b860211000000075029cbac000000000000000000

1 output(s) for total of 3.035503829000 dcy

stealth address amount amount idx
00: fdbffb429bc708aa5cce560df7d588a5087ffcb89a88526c5f8dc6e3ef35e1d4 3.035503829000 1138848 of 0

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": 695899, "vin": [ { "gen": { "height": 695889 } } ], "vout": [ { "amount": 3035503829, "target": { "key": "fdbffb429bc708aa5cce560df7d588a5087ffcb89a88526c5f8dc6e3ef35e1d4" } } ], "extra": [ 1, 146, 168, 172, 129, 239, 156, 232, 100, 75, 223, 248, 219, 198, 74, 22, 254, 203, 16, 221, 47, 82, 230, 29, 78, 214, 8, 14, 251, 138, 245, 11, 134, 2, 17, 0, 0, 0, 7, 80, 41, 203, 172, 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