Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9399a871a7314564dc4e10a2e7855b1092b0310369ba269987f5635ee12a319

Tx prefix hash: 1a0d1f8ac315aeadf882c7eecb661aef215a1272fa6a1515692cffe27bee5e72
Tx public key: e3354494e8b2117c6aecb5df9cc34ee2376cfdc44f28dfe93a2375e987ad1b93
Timestamp: 1706226000 Timestamp [UCT]: 2024-01-25 23:40:00 Age [y:d:h:m:s]: 01:030:14:18:11
Block: 943333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282926 RingCT/type: yes/0
Extra: 01e3354494e8b2117c6aecb5df9cc34ee2376cfdc44f28dfe93a2375e987ad1b930211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28e0702cdc762f3ec329a3352f0d2bbce7f129f30dfe3a03a1db5968031fda68 0.600000000000 1401539 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": 943343, "vin": [ { "gen": { "height": 943333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28e0702cdc762f3ec329a3352f0d2bbce7f129f30dfe3a03a1db5968031fda68" } } ], "extra": [ 1, 227, 53, 68, 148, 232, 178, 17, 124, 106, 236, 181, 223, 156, 195, 78, 226, 55, 108, 253, 196, 79, 40, 223, 233, 58, 35, 117, 233, 135, 173, 27, 147, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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