Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c231eb41d6de274dfc61ffe597bea648b79042fd33d3a22f26bd7ef844132c84

Tx prefix hash: 14c594c3779d301e3dc875f901337c8c86d8cd4c74958f534eed1f86d2588236
Tx public key: 2c115e5f41a8573e6db4a672038f30f9147a2fb770a13c0bfa0daf0a8c6baf18
Timestamp: 1734953164 Timestamp [UCT]: 2024-12-23 11:26:04 Age [y:d:h:m:s]: 00:123:20:05:58
Block: 1181435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88279 RingCT/type: yes/0
Extra: 012c115e5f41a8573e6db4a672038f30f9147a2fb770a13c0bfa0daf0a8c6baf18021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a6aadfb00de6b6db34d72891d7402dc06303e0036bf7bf40b6551900a52665c 0.600000000000 1667856 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": 1181445, "vin": [ { "gen": { "height": 1181435 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a6aadfb00de6b6db34d72891d7402dc06303e0036bf7bf40b6551900a52665c" } } ], "extra": [ 1, 44, 17, 94, 95, 65, 168, 87, 62, 109, 180, 166, 114, 3, 143, 48, 249, 20, 122, 47, 183, 112, 161, 60, 11, 250, 13, 175, 10, 140, 107, 175, 24, 2, 17, 0, 0, 0, 1, 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