Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e192c6a91b99cd129e4a5e27726aabdcc6def0bc5a8d2380aab2ec889165ea2e

Tx prefix hash: 36ab2865005ffa006f01c9ea9b85fe5b13741f6459eab727b0e071cfe0e489e3
Tx public key: 34434142932b8b3f98eb70a99bd34cef28481f8c24e6a675468a37bd450bdc1a
Timestamp: 1704361731 Timestamp [UCT]: 2024-01-04 09:48:51 Age [y:d:h:m:s]: 01:150:14:30:43
Block: 927915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368770 RingCT/type: yes/0
Extra: 0134434142932b8b3f98eb70a99bd34cef28481f8c24e6a675468a37bd450bdc1a02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb3bf58e8c4aacad4cf88cde212d1a679483e72d3f4673ac54014ee4ebe9b4a0 0.600000000000 1385757 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": 927925, "vin": [ { "gen": { "height": 927915 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb3bf58e8c4aacad4cf88cde212d1a679483e72d3f4673ac54014ee4ebe9b4a0" } } ], "extra": [ 1, 52, 67, 65, 66, 147, 43, 139, 63, 152, 235, 112, 169, 155, 211, 76, 239, 40, 72, 31, 140, 36, 230, 166, 117, 70, 138, 55, 189, 69, 11, 220, 26, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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