Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5c0b56363b1ed9705cbd71ee9d48504bb1a7f1a426d4a0b9dcb0e5814d4df10

Tx prefix hash: 0c744a2aa386612250316b8a844294f1870058ca23adb4217a0467bcf09f52a7
Tx public key: 8b10791a6573bc7e74ff2544263e1fe99fedfe2b7a0ee413abbe3e24d3045ac0
Timestamp: 1685901915 Timestamp [UCT]: 2023-06-04 18:05:15 Age [y:d:h:m:s]: 02:159:19:59:15
Block: 775114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 634012 RingCT/type: yes/0
Extra: 018b10791a6573bc7e74ff2544263e1fe99fedfe2b7a0ee413abbe3e24d3045ac00211000000014b8f5122000000000000000000

1 output(s) for total of 1.658539118000 dcy

stealth address amount amount idx
00: 0a955ee88bf71eb3ce9bec11f29d251fef2c5f57236308b8bb5d5def2a839957 1.658539118000 1224613 of 0

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": 775124, "vin": [ { "gen": { "height": 775114 } } ], "vout": [ { "amount": 1658539118, "target": { "key": "0a955ee88bf71eb3ce9bec11f29d251fef2c5f57236308b8bb5d5def2a839957" } } ], "extra": [ 1, 139, 16, 121, 26, 101, 115, 188, 126, 116, 255, 37, 68, 38, 62, 31, 233, 159, 237, 254, 43, 122, 14, 228, 19, 171, 190, 62, 36, 211, 4, 90, 192, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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