Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c64b265bd2bbb078da982b36dd2746f296c78b142e0177e41ed73098ba24e19

Tx prefix hash: 5b8554712a33ec13807844825139c67f767de0a41721061ee0e8785ae59a2f11
Tx public key: bcfb6caa42cdb62e1d456ed1ea1311f8b0dad9811c11a5572a798d7e4cddaf4a
Timestamp: 1738900778 Timestamp [UCT]: 2025-02-07 03:59:38 Age [y:d:h:m:s]: 00:287:13:50:58
Block: 1213828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203277 RingCT/type: yes/0
Extra: 01bcfb6caa42cdb62e1d456ed1ea1311f8b0dad9811c11a5572a798d7e4cddaf4a021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 867176f53077ed6a2f96a53c07c0c20e62ff129f0a0613dac8db062c0c77b1f4 0.600000000000 1700609 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": 1213838, "vin": [ { "gen": { "height": 1213828 } } ], "vout": [ { "amount": 600000000, "target": { "key": "867176f53077ed6a2f96a53c07c0c20e62ff129f0a0613dac8db062c0c77b1f4" } } ], "extra": [ 1, 188, 251, 108, 170, 66, 205, 182, 46, 29, 69, 110, 209, 234, 19, 17, 248, 176, 218, 217, 129, 28, 17, 165, 87, 42, 121, 141, 126, 76, 221, 175, 74, 2, 17, 0, 0, 0, 6, 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