Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34b91fce54e2615b948e1cc296f29cb5ea4f5e58757a817427b0daca7be644fc

Tx prefix hash: 9eec84d9c63856a91266b086a1c7cea9eafaab8f305460e7ec7daf8e241882b7
Tx public key: fd7976dca6d166f6428421dfd2013007a21515d0bd4ead77dc06079c68a83cff
Timestamp: 1709072415 Timestamp [UCT]: 2024-02-27 22:20:15 Age [y:d:h:m:s]: 00:254:04:40:38
Block: 966973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181983 RingCT/type: yes/0
Extra: 01fd7976dca6d166f6428421dfd2013007a21515d0bd4ead77dc06079c68a83cff02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80b6a04f320986a48f0996c375c8fd41e3f773b8016da8c7cae35fe402cd6340 0.600000000000 1426744 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": 966983, "vin": [ { "gen": { "height": 966973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80b6a04f320986a48f0996c375c8fd41e3f773b8016da8c7cae35fe402cd6340" } } ], "extra": [ 1, 253, 121, 118, 220, 166, 209, 102, 246, 66, 132, 33, 223, 210, 1, 48, 7, 162, 21, 21, 208, 189, 78, 173, 119, 220, 6, 7, 156, 104, 168, 60, 255, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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