Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1db114a51a5bb54fd3e3f416c96188baaf9d6b6f6c1a0a2a65cf72dd30198b97

Tx prefix hash: b5ba9ceb9b1ff8a0406fe5c65bcfb87cafca6b8e44baeecd1968217e2fc22976
Tx public key: c6145b4328f7b5224c5b2a9c716750cf463f85224dcb2b41e745feb64bdbc7c0
Timestamp: 1700832111 Timestamp [UCT]: 2023-11-24 13:21:51 Age [y:d:h:m:s]: 01:136:09:23:25
Block: 898641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358638 RingCT/type: yes/0
Extra: 01c6145b4328f7b5224c5b2a9c716750cf463f85224dcb2b41e745feb64bdbc7c0021100000003faf35c9c000000000000000000

1 output(s) for total of 0.646292787000 dcy

stealth address amount amount idx
00: 9aa1f4fb1b21e832ff3819162a8f26ecfb225e388ceca4abca1fb9277ca51dc3 0.646292787000 1355066 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": 898651, "vin": [ { "gen": { "height": 898641 } } ], "vout": [ { "amount": 646292787, "target": { "key": "9aa1f4fb1b21e832ff3819162a8f26ecfb225e388ceca4abca1fb9277ca51dc3" } } ], "extra": [ 1, 198, 20, 91, 67, 40, 247, 181, 34, 76, 91, 42, 156, 113, 103, 80, 207, 70, 63, 133, 34, 77, 203, 43, 65, 231, 69, 254, 182, 75, 219, 199, 192, 2, 17, 0, 0, 0, 3, 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