Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd30081330d274a6162d7a2b1dbc3d4ad3cde67e66ee9c60335fd7c684f80638

Tx prefix hash: 73baaef78d9f028b07cf860be852df43dfc2a3fb6c62f5b4da19bcbee70328c6
Tx public key: 2f69e2562b2c143d0ef4748bf96bd63f28ea01464ce66d289078c767c4133831
Timestamp: 1710805163 Timestamp [UCT]: 2024-03-18 23:39:23 Age [y:d:h:m:s]: 01:016:10:55:31
Block: 981344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272725 RingCT/type: yes/0
Extra: 012f69e2562b2c143d0ef4748bf96bd63f28ea01464ce66d289078c767c4133831021100000001a5df9d86000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a7ab51271149b4bd93f67e36f7068a358e7d38d4e4ae407e8bbaa7c719fdb73 0.600000000000 1441439 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": 981354, "vin": [ { "gen": { "height": 981344 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a7ab51271149b4bd93f67e36f7068a358e7d38d4e4ae407e8bbaa7c719fdb73" } } ], "extra": [ 1, 47, 105, 226, 86, 43, 44, 20, 61, 14, 244, 116, 139, 249, 107, 214, 63, 40, 234, 1, 70, 76, 230, 109, 40, 144, 120, 199, 103, 196, 19, 56, 49, 2, 17, 0, 0, 0, 1, 165, 223, 157, 134, 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