Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 673d6059c8e54ae530c789b23774ac624ba3a6481c69eeac74ed8de767b30f88

Tx prefix hash: 16bd55743979bd2ee1f594c56d48cf0d0406d540e8b1f081a11daea49c2bb88b
Tx public key: 8cf5799e383c8b19ca4b36c9a9d4148b9a2622a93d4970df7621ebcedd121493
Timestamp: 1723045371 Timestamp [UCT]: 2024-08-07 15:42:51 Age [y:d:h:m:s]: 00:295:02:19:51
Block: 1082803 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210837 RingCT/type: yes/0
Extra: 018cf5799e383c8b19ca4b36c9a9d4148b9a2622a93d4970df7621ebcedd12149302110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8277c9b6121fbcccd4b0da51b7ef18b1f6e1b5ddddfc1326f6dfab2922386e14 0.600000000000 1556634 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": 1082813, "vin": [ { "gen": { "height": 1082803 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8277c9b6121fbcccd4b0da51b7ef18b1f6e1b5ddddfc1326f6dfab2922386e14" } } ], "extra": [ 1, 140, 245, 121, 158, 56, 60, 139, 25, 202, 75, 54, 201, 169, 212, 20, 139, 154, 38, 34, 169, 61, 73, 112, 223, 118, 33, 235, 206, 221, 18, 20, 147, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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