Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7bc87f0ac96a6fcbb8a7164259ee97ad70eb9ae429589cb6ce0cd7e76d60f733

Tx prefix hash: 06aee1884961b2f65f912d1e9207124be6871f3dbf91ca5a55485f5e7970181c
Tx public key: f82614d0035482ae08cc7129027d3d1fa562f29dfa65f5e74601f9a9873ecf1f
Timestamp: 1699714274 Timestamp [UCT]: 2023-11-11 14:51:14 Age [y:d:h:m:s]: 01:113:07:36:56
Block: 889381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342149 RingCT/type: yes/0
Extra: 01f82614d0035482ae08cc7129027d3d1fa562f29dfa65f5e74601f9a9873ecf1f021100000002faf35c9c000000000000000000

1 output(s) for total of 0.693603932000 dcy

stealth address amount amount idx
00: 0c17d84a141caac1bd21ed573e99090f909432c42de2a9d8efb5571cf84388f6 0.693603932000 1345378 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": 889391, "vin": [ { "gen": { "height": 889381 } } ], "vout": [ { "amount": 693603932, "target": { "key": "0c17d84a141caac1bd21ed573e99090f909432c42de2a9d8efb5571cf84388f6" } } ], "extra": [ 1, 248, 38, 20, 208, 3, 84, 130, 174, 8, 204, 113, 41, 2, 125, 61, 31, 165, 98, 242, 157, 250, 101, 245, 231, 70, 1, 249, 169, 135, 62, 207, 31, 2, 17, 0, 0, 0, 2, 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