Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 810aa8049347e5b74fca9b8a43547839909acc193d48bbc96620abeb15252717

Tx prefix hash: 36191e4d2cc36740fc54c83d0c23bf26c77cc58402e8f234f7c5230110f95a8d
Tx public key: 7c0dc715fc5e300385f9e8ddcb83d275583c517c1e18c15e79d9a55cf28149c3
Timestamp: 1738958115 Timestamp [UCT]: 2025-02-07 19:55:15 Age [y:d:h:m:s]: 00:286:00:39:49
Block: 1214298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202173 RingCT/type: yes/0
Extra: 017c0dc715fc5e300385f9e8ddcb83d275583c517c1e18c15e79d9a55cf28149c3021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5ae749fab08b8302c40dbd5bbc174d0c325a066c5ecadeb208496e2fc696b41 0.600000000000 1701087 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": 1214308, "vin": [ { "gen": { "height": 1214298 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5ae749fab08b8302c40dbd5bbc174d0c325a066c5ecadeb208496e2fc696b41" } } ], "extra": [ 1, 124, 13, 199, 21, 252, 94, 48, 3, 133, 249, 232, 221, 203, 131, 210, 117, 88, 60, 81, 124, 30, 24, 193, 94, 121, 217, 165, 92, 242, 129, 73, 195, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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