Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba67cd474788e192d871b5ad187a5c8b20b1de88cbd288bd75a6065b47fe73c9

Tx prefix hash: 861ac371d4ab71a1ec90aacdfd2d7ef8bee2205d0557278287a1638759bc0162
Tx public key: 68b2cb012e63439bd1f215943da706b2725edb93d4c1dd3e7049dea7c784ce3a
Timestamp: 1736779292 Timestamp [UCT]: 2025-01-13 14:41:32 Age [y:d:h:m:s]: 00:064:03:21:45
Block: 1196523 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45623 RingCT/type: yes/0
Extra: 0168b2cb012e63439bd1f215943da706b2725edb93d4c1dd3e7049dea7c784ce3a0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8f34949f65df4d8123de2cc26145a224aac877a4aaeadd1cdd5314a3dbc47f8 0.600000000000 1683122 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": 1196533, "vin": [ { "gen": { "height": 1196523 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8f34949f65df4d8123de2cc26145a224aac877a4aaeadd1cdd5314a3dbc47f8" } } ], "extra": [ 1, 104, 178, 203, 1, 46, 99, 67, 155, 209, 242, 21, 148, 61, 167, 6, 178, 114, 94, 219, 147, 212, 193, 221, 62, 112, 73, 222, 167, 199, 132, 206, 58, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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