Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84111e980d9e845aafea18c064a66aae356155c458f20fcf5ff74b598ef5a2ab

Tx prefix hash: 69e87b5bc95cb9d1228505809ff3be64d7b64f2a209cb8670aafbfcfb1d91418
Tx public key: 583eaacc5d3fe946d2b75332e3880cfa47872fdc4777d8be2d8b2b564a26c7cc
Timestamp: 1705707299 Timestamp [UCT]: 2024-01-19 23:34:59 Age [y:d:h:m:s]: 00:362:01:17:59
Block: 939026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259224 RingCT/type: yes/0
Extra: 01583eaacc5d3fe946d2b75332e3880cfa47872fdc4777d8be2d8b2b564a26c7cc02110000000179bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6383c9c9c09973ed3f9c4d1b06fa65dcbf1414f214fc9aa9c43b0698c72f3335 0.600000000000 1397110 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": 939036, "vin": [ { "gen": { "height": 939026 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6383c9c9c09973ed3f9c4d1b06fa65dcbf1414f214fc9aa9c43b0698c72f3335" } } ], "extra": [ 1, 88, 62, 170, 204, 93, 63, 233, 70, 210, 183, 83, 50, 227, 136, 12, 250, 71, 135, 47, 220, 71, 119, 216, 190, 45, 139, 43, 86, 74, 38, 199, 204, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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