Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 953ee85e74238991978299505b1f6ff7062aeee81d3f556f1515ebf49f04bfea

Tx prefix hash: 094d4f530ccb7cf5db6e5a6bdf851b64e6becd816af39c2e426ae191e757e242
Tx public key: a6f651df887c213a72e238138d87ae1156112be3ada19c6df17ea8f6863f3a65
Timestamp: 1721608561 Timestamp [UCT]: 2024-07-22 00:36:01 Age [y:d:h:m:s]: 00:289:20:38:26
Block: 1070877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207111 RingCT/type: yes/0
Extra: 01a6f651df887c213a72e238138d87ae1156112be3ada19c6df17ea8f6863f3a65021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f60da366c566e39dce3c471718e99a84139bd586b1539bdf931057ca95975e62 0.600000000000 1542892 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": 1070887, "vin": [ { "gen": { "height": 1070877 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f60da366c566e39dce3c471718e99a84139bd586b1539bdf931057ca95975e62" } } ], "extra": [ 1, 166, 246, 81, 223, 136, 124, 33, 58, 114, 226, 56, 19, 141, 135, 174, 17, 86, 17, 43, 227, 173, 161, 156, 109, 241, 126, 168, 246, 134, 63, 58, 101, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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