Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08690e1db603b8416800951a4115490fc265a6c48def0d125f8354de8227f57e

Tx prefix hash: 812dcadbecf643bd0ca4b721f5d9a47e94dc8c16a3dbfb3a5a5a2febf3d33d80
Tx public key: 02bfa10de9703ea753f5cf293d5a623d4a01a1ba02be1f83fdf25c6fa933da6e
Timestamp: 1631427471 Timestamp [UCT]: 2021-09-12 06:17:51 Age [y:d:h:m:s]: 03:118:08:52:39
Block: 332117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 860136 RingCT/type: yes/0
Extra: 0102bfa10de9703ea753f5cf293d5a623d4a01a1ba02be1f83fdf25c6fa933da6e0211000000015410958b000000000000000000

1 output(s) for total of 48.703363396000 dcy

stealth address amount amount idx
00: cc0067b11d3d8d326011d9ac726509f7305e0b4a9e55c1cf050a55b2d64fa483 48.703363396000 685982 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": 332127, "vin": [ { "gen": { "height": 332117 } } ], "vout": [ { "amount": 48703363396, "target": { "key": "cc0067b11d3d8d326011d9ac726509f7305e0b4a9e55c1cf050a55b2d64fa483" } } ], "extra": [ 1, 2, 191, 161, 13, 233, 112, 62, 167, 83, 245, 207, 41, 61, 90, 98, 61, 74, 1, 161, 186, 2, 190, 31, 131, 253, 242, 92, 111, 169, 51, 218, 110, 2, 17, 0, 0, 0, 1, 84, 16, 149, 139, 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