Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47d14fabf5ffa93ed5d09ea2c28576a723eee02e3577e16628a42fe4ca2989f2

Tx prefix hash: a81ddc9aa4dcc7142216951b6bde07e0fb4f622118e8db101b068dfd64c099c2
Tx public key: f786a43d1cd9da009cdb27bfc4dd56bfb3d7187d34ec517fa5f06d1677263da4
Timestamp: 1725084086 Timestamp [UCT]: 2024-08-31 06:01:26 Age [y:d:h:m:s]: 01:068:13:31:00
Block: 1099702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307438 RingCT/type: yes/0
Extra: 01f786a43d1cd9da009cdb27bfc4dd56bfb3d7187d34ec517fa5f06d1677263da4021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c06dc9f821c97f2b4690638eb8b3faa8d881ce1738c39b04d4c7e125cc388a4b 0.600000000000 1575667 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": 1099712, "vin": [ { "gen": { "height": 1099702 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c06dc9f821c97f2b4690638eb8b3faa8d881ce1738c39b04d4c7e125cc388a4b" } } ], "extra": [ 1, 247, 134, 164, 61, 28, 217, 218, 0, 156, 219, 39, 191, 196, 221, 86, 191, 179, 215, 24, 125, 52, 236, 81, 127, 165, 240, 109, 22, 119, 38, 61, 164, 2, 17, 0, 0, 0, 1, 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