Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85a57cf154a89451eccfb6526a03fb07d535d77903d8381c269954f69705c953

Tx prefix hash: 98d9b7382016f0417b1dcecd3772b059aa2e7982886ed7a5eb791a0655c6743d
Tx public key: ca2b2430441c1e569a103928b9abb307b74c7a90e376f9e95ac596e73c8d3c1b
Timestamp: 1717102601 Timestamp [UCT]: 2024-05-30 20:56:41 Age [y:d:h:m:s]: 00:263:02:15:50
Block: 1033530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187986 RingCT/type: yes/0
Extra: 01ca2b2430441c1e569a103928b9abb307b74c7a90e376f9e95ac596e73c8d3c1b02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 641b37e16719654753cdd2a56bc0ca10da653e5cb17fc2fb8046f3c5c39a8da3 0.600000000000 1501999 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": 1033540, "vin": [ { "gen": { "height": 1033530 } } ], "vout": [ { "amount": 600000000, "target": { "key": "641b37e16719654753cdd2a56bc0ca10da653e5cb17fc2fb8046f3c5c39a8da3" } } ], "extra": [ 1, 202, 43, 36, 48, 68, 28, 30, 86, 154, 16, 57, 40, 185, 171, 179, 7, 183, 76, 122, 144, 227, 118, 249, 233, 90, 197, 150, 231, 60, 141, 60, 27, 2, 17, 0, 0, 0, 6, 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