Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 367cf372de0bfb7d45d4a3e392a2b6fccca5ae8293a981ecc6dee6a56754e8ec

Tx prefix hash: 2616249914374d8fc9d00c0cf7ff2f23bc609b39fa10daeb55fe9d1ae051dda2
Tx public key: ca7f1c9a02608396a8d3f1a566a7b8113448795796dd98512f70170f08236e02
Timestamp: 1734143007 Timestamp [UCT]: 2024-12-14 02:23:27 Age [y:d:h:m:s]: 00:111:08:53:08
Block: 1174713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79375 RingCT/type: yes/0
Extra: 01ca7f1c9a02608396a8d3f1a566a7b8113448795796dd98512f70170f08236e02021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81a0ad4f047f1984ccddd4fa3e5319c9a0634c2623fdc0f0a3d2fb2b18df1007 0.600000000000 1660900 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": 1174723, "vin": [ { "gen": { "height": 1174713 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81a0ad4f047f1984ccddd4fa3e5319c9a0634c2623fdc0f0a3d2fb2b18df1007" } } ], "extra": [ 1, 202, 127, 28, 154, 2, 96, 131, 150, 168, 211, 241, 165, 102, 167, 184, 17, 52, 72, 121, 87, 150, 221, 152, 81, 47, 112, 23, 15, 8, 35, 110, 2, 2, 17, 0, 0, 0, 5, 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