Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b085bec0649e07c4d8c3ba31f6639ca144b8766cfdef8916b388350ac6b9703

Tx prefix hash: 5d9d6125c13f7feba105f084caac6fad50005d9b30b61a0ca7867903d0f9a8ab
Tx public key: 9ae551bf2f6d029c34f691a3838344cc4b90f8db84112e67fb392870c6ef51c5
Timestamp: 1725300314 Timestamp [UCT]: 2024-09-02 18:05:14 Age [y:d:h:m:s]: 00:211:16:14:44
Block: 1101494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151132 RingCT/type: yes/0
Extra: 019ae551bf2f6d029c34f691a3838344cc4b90f8db84112e67fb392870c6ef51c5021100000002e914dd15000000000000000000

1 output(s) for total of 0.608000000000 dcy

stealth address amount amount idx
00: 82ad9ba97d4ee7ed431d9014dac1dc6f2e1255e53ec6b474f12de50d1f916758 0.608000000000 1577565 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": 1101504, "vin": [ { "gen": { "height": 1101494 } } ], "vout": [ { "amount": 608000000, "target": { "key": "82ad9ba97d4ee7ed431d9014dac1dc6f2e1255e53ec6b474f12de50d1f916758" } } ], "extra": [ 1, 154, 229, 81, 191, 47, 109, 2, 156, 52, 246, 145, 163, 131, 131, 68, 204, 75, 144, 248, 219, 132, 17, 46, 103, 251, 57, 40, 112, 198, 239, 81, 197, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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