Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9a17faa73cd152a15d16deac4f7f0a116b39efb8028a65eca72a22cfa1739cc

Tx prefix hash: f97f3c216f8c4edc881d34c6e81be7bdcb5d86fa228f08d93bbde0d94e6c2010
Tx public key: 0d3b2e8991e5a73fb15e9ffe4fd515299fcec1d70b4d491054aac33c496e2307
Timestamp: 1732500850 Timestamp [UCT]: 2024-11-25 02:14:10 Age [y:d:h:m:s]: 00:129:16:20:04
Block: 1161091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92488 RingCT/type: yes/0
Extra: 010d3b2e8991e5a73fb15e9ffe4fd515299fcec1d70b4d491054aac33c496e23070211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72f3b341938e2d8f4482b487264dcafd2c650de408060b50c6cb52d5bd28e03e 0.600000000000 1646742 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": 1161101, "vin": [ { "gen": { "height": 1161091 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72f3b341938e2d8f4482b487264dcafd2c650de408060b50c6cb52d5bd28e03e" } } ], "extra": [ 1, 13, 59, 46, 137, 145, 229, 167, 63, 177, 94, 159, 254, 79, 213, 21, 41, 159, 206, 193, 215, 11, 77, 73, 16, 84, 170, 195, 60, 73, 110, 35, 7, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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