Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 823d36312b8e73441b67eb5b8fc49c152fc607dc531df59907e4877722b41c6f

Tx prefix hash: 6b9be8bc46be55e1c7b2ff2f45858d4a5bce12693857029ebebab0bea1ef2dce
Tx public key: 7c3fc7c5a0adc894b0cfe98e923235b4961f03570f0a0fa79f465ee170bbf994
Timestamp: 1716695385 Timestamp [UCT]: 2024-05-26 03:49:45 Age [y:d:h:m:s]: 00:312:22:18:12
Block: 1030165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223642 RingCT/type: yes/0
Extra: 017c3fc7c5a0adc894b0cfe98e923235b4961f03570f0a0fa79f465ee170bbf99402110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b50f6caec827cd02a48832781000fa2980f23b9e0df83c650f242c3d9dff560c 0.600000000000 1498418 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": 1030175, "vin": [ { "gen": { "height": 1030165 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b50f6caec827cd02a48832781000fa2980f23b9e0df83c650f242c3d9dff560c" } } ], "extra": [ 1, 124, 63, 199, 197, 160, 173, 200, 148, 176, 207, 233, 142, 146, 50, 53, 180, 150, 31, 3, 87, 15, 10, 15, 167, 159, 70, 94, 225, 112, 187, 249, 148, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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