Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 969fc64e98771b2b5eaeda81d178982cf735e09e080bf2d4f970f4c6ccda6058

Tx prefix hash: b246de007ac6242a5fcd28cc4e7b09636f830af2f79d397ed0c7106c4f1f9c1f
Tx public key: d938fdaccad5d9e95f804fc05c8a7447ada9f13a754efaec73bce5f3d0728962
Timestamp: 1695250704 Timestamp [UCT]: 2023-09-20 22:58:24 Age [y:d:h:m:s]: 01:263:09:08:49
Block: 852565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 449368 RingCT/type: yes/0
Extra: 01d938fdaccad5d9e95f804fc05c8a7447ada9f13a754efaec73bce5f3d0728962021100000006faf35c9c000000000000000000

1 output(s) for total of 0.918540461000 dcy

stealth address amount amount idx
00: a05b4c58c3f50a45b207c5f25d099849ef692c645c4257ce04c83df7c9ab7d2b 0.918540461000 1306409 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": 852575, "vin": [ { "gen": { "height": 852565 } } ], "vout": [ { "amount": 918540461, "target": { "key": "a05b4c58c3f50a45b207c5f25d099849ef692c645c4257ce04c83df7c9ab7d2b" } } ], "extra": [ 1, 217, 56, 253, 172, 202, 213, 217, 233, 95, 128, 79, 192, 92, 138, 116, 71, 173, 169, 241, 58, 117, 78, 250, 236, 115, 188, 229, 243, 208, 114, 137, 98, 2, 17, 0, 0, 0, 6, 250, 243, 92, 156, 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