Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8ea6704991c20f11c0e2c50fdafc55eac7e70a3f1765847cacc91258a927e12

Tx prefix hash: 9889411f31c32274c8650004aa0ec5140d2db689ed6d8241c70b5a73819ad4ae
Tx public key: 14e93127b46d9922d528db681912fdbebc6b0c84aecad77d1bc7f84d05e9cf82
Timestamp: 1738162336 Timestamp [UCT]: 2025-01-29 14:52:16 Age [y:d:h:m:s]: 00:139:01:06:42
Block: 1207709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99341 RingCT/type: yes/0
Extra: 0114e93127b46d9922d528db681912fdbebc6b0c84aecad77d1bc7f84d05e9cf820211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7543fbfb179bb6e06af4320eee48ceeb6f1712f26e4d5eb204fc089dceed4e2 0.600000000000 1694434 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": 1207719, "vin": [ { "gen": { "height": 1207709 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7543fbfb179bb6e06af4320eee48ceeb6f1712f26e4d5eb204fc089dceed4e2" } } ], "extra": [ 1, 20, 233, 49, 39, 180, 109, 153, 34, 213, 40, 219, 104, 25, 18, 253, 190, 188, 107, 12, 132, 174, 202, 215, 125, 27, 199, 248, 77, 5, 233, 207, 130, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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