Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5605febaf3527b2e8cb3d6106731d80fac1c0dec1038c72705ea9d6d880ac3d1

Tx prefix hash: 75e377be456bf63af920f094c0da075e78ee051a04e1775ef8b438832d01bbb1
Tx public key: ec4f8b7c14edd39fafaf24e1c93f5e01e64e5769ecbda6693159e97c4ff2a942
Timestamp: 1710126079 Timestamp [UCT]: 2024-03-11 03:01:19 Age [y:d:h:m:s]: 01:079:12:40:28
Block: 975704 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317869 RingCT/type: yes/0
Extra: 01ec4f8b7c14edd39fafaf24e1c93f5e01e64e5769ecbda6693159e97c4ff2a94202110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0aa4374400dbce4feb6d224391520e516724497ba1f7ee2c0e17727e36722df0 0.600000000000 1435677 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": 975714, "vin": [ { "gen": { "height": 975704 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0aa4374400dbce4feb6d224391520e516724497ba1f7ee2c0e17727e36722df0" } } ], "extra": [ 1, 236, 79, 139, 124, 20, 237, 211, 159, 175, 175, 36, 225, 201, 63, 94, 1, 230, 78, 87, 105, 236, 189, 166, 105, 49, 89, 233, 124, 79, 242, 169, 66, 2, 17, 0, 0, 0, 10, 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