Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 423aaf4a4f17839865b5d83924cb99fe2b427db3b682d5ca7ba54cf48e24bc3f

Tx prefix hash: 48ee9cf4a8387504c7abb9aa83aab98346e72b4b7fde30bda0fb3ef24d39579f
Tx public key: 3706cb85efbd50dba1bbb15aaccc1369c26b49cc50af1a0be819477c17e54a31
Timestamp: 1704991792 Timestamp [UCT]: 2024-01-11 16:49:52 Age [y:d:h:m:s]: 00:308:13:55:33
Block: 933124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220940 RingCT/type: yes/0
Extra: 013706cb85efbd50dba1bbb15aaccc1369c26b49cc50af1a0be819477c17e54a310211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b8cb5803d86e6b96edd6fc7326f0c4ff3a935e9d686f2468cc8f0497845115a 0.600000000000 1391080 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": 933134, "vin": [ { "gen": { "height": 933124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b8cb5803d86e6b96edd6fc7326f0c4ff3a935e9d686f2468cc8f0497845115a" } } ], "extra": [ 1, 55, 6, 203, 133, 239, 189, 80, 219, 161, 187, 177, 90, 172, 204, 19, 105, 194, 107, 73, 204, 80, 175, 26, 11, 232, 25, 71, 124, 23, 229, 74, 49, 2, 17, 0, 0, 0, 4, 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