Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1fa1bce5dcfe83215017b8e0b57421c7fccd960cc863fde28d7783c85e75564

Tx prefix hash: 6da5dbfc27efd6cba0076b480c7059fb5282e743744aeaa62f6117de5f1cd606
Tx public key: 4b281007b5caa4d3dbd4203f61f6d917ade479b8b46993fafd734393f910b6e5
Timestamp: 1693186684 Timestamp [UCT]: 2023-08-28 01:38:04 Age [y:d:h:m:s]: 01:227:07:02:41
Block: 835428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 423591 RingCT/type: yes/0
Extra: 014b281007b5caa4d3dbd4203f61f6d917ade479b8b46993fafd734393f910b6e5021100000001faf35c9c000000000000000000

1 output(s) for total of 1.046840006000 dcy

stealth address amount amount idx
00: 8c2bc7c0e50c72fb90eacad9db6572d514c01464954ab7ee4f660a9a380ef44a 1.046840006000 1287978 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": 835438, "vin": [ { "gen": { "height": 835428 } } ], "vout": [ { "amount": 1046840006, "target": { "key": "8c2bc7c0e50c72fb90eacad9db6572d514c01464954ab7ee4f660a9a380ef44a" } } ], "extra": [ 1, 75, 40, 16, 7, 181, 202, 164, 211, 219, 212, 32, 63, 97, 246, 217, 23, 173, 228, 121, 184, 180, 105, 147, 250, 253, 115, 67, 147, 249, 16, 182, 229, 2, 17, 0, 0, 0, 1, 250, 243, 92, 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