Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 164ced0c7a5bd906f97a6411cea571fef26b4391e9d5ac3776e97c489ca7298d

Tx prefix hash: 932b1b6b36cc77f49a8c3060689e459096c6cec6d300d10c5e760005b94e89c4
Tx public key: 687f214766701ad0df25492a6ab3e6335df26981d33cb6136a768d8fb25137e7
Timestamp: 1673602971 Timestamp [UCT]: 2023-01-13 09:42:51 Age [y:d:h:m:s]: 02:084:23:01:39
Block: 673766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 582385 RingCT/type: yes/0
Extra: 01687f214766701ad0df25492a6ab3e6335df26981d33cb6136a768d8fb25137e70211000000038b7b6602000000000000000000

1 output(s) for total of 3.593631159000 dcy

stealth address amount amount idx
00: ee6f28ebcba8dc224b5d910ed1fe7d8bb6030941c5d65cc6e341d5bb54bbbd80 3.593631159000 1115389 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": 673776, "vin": [ { "gen": { "height": 673766 } } ], "vout": [ { "amount": 3593631159, "target": { "key": "ee6f28ebcba8dc224b5d910ed1fe7d8bb6030941c5d65cc6e341d5bb54bbbd80" } } ], "extra": [ 1, 104, 127, 33, 71, 102, 112, 26, 208, 223, 37, 73, 42, 106, 179, 230, 51, 93, 242, 105, 129, 211, 60, 182, 19, 106, 118, 141, 143, 178, 81, 55, 231, 2, 17, 0, 0, 0, 3, 139, 123, 102, 2, 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