Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9031da3e5e6d24522d031410f17f14622d7111be7027280e549ad7a627dc447

Tx prefix hash: 961f4f20e1e68049b7da3c4189ff462e76b01013234d6e6a7208c9d927fa297a
Tx public key: 92ae34222e2d6380c5efef30e189c8e9f241b8eb71f73cd55e205675fabe4b71
Timestamp: 1731260909 Timestamp [UCT]: 2024-11-10 17:48:29 Age [y:d:h:m:s]: 00:013:12:44:38
Block: 1150828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9676 RingCT/type: yes/0
Extra: 0192ae34222e2d6380c5efef30e189c8e9f241b8eb71f73cd55e205675fabe4b7102110000000168ce33d7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29c1e91908f95f78ef6f2b60c1f97dd1204df47d7afd7460980e6e00e3cafdee 0.600000000000 1636239 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": 1150838, "vin": [ { "gen": { "height": 1150828 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29c1e91908f95f78ef6f2b60c1f97dd1204df47d7afd7460980e6e00e3cafdee" } } ], "extra": [ 1, 146, 174, 52, 34, 46, 45, 99, 128, 197, 239, 239, 48, 225, 137, 200, 233, 242, 65, 184, 235, 113, 247, 60, 213, 94, 32, 86, 117, 250, 190, 75, 113, 2, 17, 0, 0, 0, 1, 104, 206, 51, 215, 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