Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 760aa63d83714e154422bf27cc92d0d4a40af3c0564af5cc642ef8c95053349f

Tx prefix hash: 1e4c3590a76a4c4005807b83919a91296107058a8d22315cd86b6d130c192dd6
Tx public key: e699e07337e4a92ccec29ce547082d54f02287b0dddb602c6fc055ff83f3e7bf
Timestamp: 1729941853 Timestamp [UCT]: 2024-10-26 11:24:13 Age [y:d:h:m:s]: 00:149:09:11:13
Block: 1139945 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106546 RingCT/type: yes/0
Extra: 01e699e07337e4a92ccec29ce547082d54f02287b0dddb602c6fc055ff83f3e7bf0211000000053cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d7511b191141a9ea290a46b0c2daf9bc02e08b1db51a0df2a1653533f9ba9cc 0.600000000000 1623732 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": 1139955, "vin": [ { "gen": { "height": 1139945 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d7511b191141a9ea290a46b0c2daf9bc02e08b1db51a0df2a1653533f9ba9cc" } } ], "extra": [ 1, 230, 153, 224, 115, 55, 228, 169, 44, 206, 194, 156, 229, 71, 8, 45, 84, 240, 34, 135, 176, 221, 219, 96, 44, 111, 192, 85, 255, 131, 243, 231, 191, 2, 17, 0, 0, 0, 5, 60, 208, 252, 6, 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