Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 026402c6fd010e877a956945796ab52b384856bcb3891c2d0d583ff1591b10a4

Tx prefix hash: 2e7c82682bd9c079ce39e28f0272167bc5ba1dbc67d1da106a149bc5e2516df9
Tx public key: a34e5f4c2ec41ce0171069bf6f021e74c0eaff40a5227dd5e4e2c743173eaac7
Timestamp: 1736181693 Timestamp [UCT]: 2025-01-06 16:41:33 Age [y:d:h:m:s]: 00:069:04:46:07
Block: 1191589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49234 RingCT/type: yes/0
Extra: 01a34e5f4c2ec41ce0171069bf6f021e74c0eaff40a5227dd5e4e2c743173eaac702110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2a2d0aa60a2c882eab91fa06c4cb727c8ce6bae522e3bca608755f6d86983d7 0.600000000000 1678128 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": 1191599, "vin": [ { "gen": { "height": 1191589 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2a2d0aa60a2c882eab91fa06c4cb727c8ce6bae522e3bca608755f6d86983d7" } } ], "extra": [ 1, 163, 78, 95, 76, 46, 196, 28, 224, 23, 16, 105, 191, 111, 2, 30, 116, 192, 234, 255, 64, 165, 34, 125, 213, 228, 226, 199, 67, 23, 62, 170, 199, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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