Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4448afcdc46a9a8fd085502db7539e98e837304390e965e460dd18dda0b18578

Tx prefix hash: 66ae2132715078d3db2ea56ceec269556b40f7a4fbf0588deee5b7098a90574d
Tx public key: f57b8da2508ccbee9cff1c49d6222eadd39bb27414c4965760f453734f5da2ac
Timestamp: 1694273524 Timestamp [UCT]: 2023-09-09 15:32:04 Age [y:d:h:m:s]: 01:206:05:12:52
Block: 844454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408481 RingCT/type: yes/0
Extra: 01f57b8da2508ccbee9cff1c49d6222eadd39bb27414c4965760f453734f5da2ac021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.977177398000 dcy

stealth address amount amount idx
00: b83e7873e075f8bdad6f5cfc2fff0064e7a12bfac043f2e051ae37b7b8546953 0.977177398000 1297764 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": 844464, "vin": [ { "gen": { "height": 844454 } } ], "vout": [ { "amount": 977177398, "target": { "key": "b83e7873e075f8bdad6f5cfc2fff0064e7a12bfac043f2e051ae37b7b8546953" } } ], "extra": [ 1, 245, 123, 141, 162, 80, 140, 203, 238, 156, 255, 28, 73, 214, 34, 46, 173, 211, 155, 178, 116, 20, 196, 150, 87, 96, 244, 83, 115, 79, 93, 162, 172, 2, 17, 0, 0, 0, 7, 230, 210, 127, 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