Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa8e9d7c30913df00255b49b1f0fa7b12163b5cd6463789dc8c46dc4091239f5

Tx prefix hash: 59bfdd1ff471a35231b484e022bc2d69a5e426058c6e5bec65a101ca5df84151
Tx public key: 18e0a0de3f6cc3ae0477db28b7a3e109e4ac4444a8e3772e64eb81b51f74a30c
Timestamp: 1672712126 Timestamp [UCT]: 2023-01-03 02:15:26 Age [y:d:h:m:s]: 01:334:12:13:46
Block: 666379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 500089 RingCT/type: yes/0
Extra: 0118e0a0de3f6cc3ae0477db28b7a3e109e4ac4444a8e3772e64eb81b51f74a30c021100000001e6d27f9c000000000000000000

1 output(s) for total of 3.801978954000 dcy

stealth address amount amount idx
00: 1251864d8caa98ac924a99dea25c7e01d1b80b8318d4ecef7d760a603bea7013 3.801978954000 1107488 of 0

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": 666389, "vin": [ { "gen": { "height": 666379 } } ], "vout": [ { "amount": 3801978954, "target": { "key": "1251864d8caa98ac924a99dea25c7e01d1b80b8318d4ecef7d760a603bea7013" } } ], "extra": [ 1, 24, 224, 160, 222, 63, 108, 195, 174, 4, 119, 219, 40, 183, 163, 225, 9, 228, 172, 68, 68, 168, 227, 119, 46, 100, 235, 129, 181, 31, 116, 163, 12, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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