Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9f8c3bfd5f6ae1dbdfa600735889aedfffd6998e388f5b80bbb917d1c8fe4d0

Tx prefix hash: 0aa30ba20fdcde9ae95a63b92d1e51569835580d994a8a84a2148261e51aafbe
Tx public key: a46ef2e7dd902d2302f9dd71d63dd9754afcc0b82d3fbe7b087673f7037ea166
Timestamp: 1705478013 Timestamp [UCT]: 2024-01-17 07:53:33 Age [y:d:h:m:s]: 01:101:01:43:58
Block: 937141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333360 RingCT/type: yes/0
Extra: 01a46ef2e7dd902d2302f9dd71d63dd9754afcc0b82d3fbe7b087673f7037ea16602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01c1b969ba6aafba8aeae28edbefb15f0b505d6513bdf4ab4cb2f7c445f15d78 0.600000000000 1395185 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": 937151, "vin": [ { "gen": { "height": 937141 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01c1b969ba6aafba8aeae28edbefb15f0b505d6513bdf4ab4cb2f7c445f15d78" } } ], "extra": [ 1, 164, 110, 242, 231, 221, 144, 45, 35, 2, 249, 221, 113, 214, 61, 217, 117, 74, 252, 192, 184, 45, 63, 190, 123, 8, 118, 115, 247, 3, 126, 161, 102, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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