Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29474cad603f44de8068fb39649b11984f68286c6f1b768ad410c5daba473aa2

Tx prefix hash: 21fc2e28e46c09d02185c6c7e48e717af5cc66c2bec9ddab277a7e07dda11f79
Tx public key: d5024b8b498241f8bce263afeae77aaaf9932452cb495e21f09602e93f88b111
Timestamp: 1726060350 Timestamp [UCT]: 2024-09-11 13:12:30 Age [y:d:h:m:s]: 01:058:03:13:47
Block: 1107796 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299971 RingCT/type: yes/0
Extra: 01d5024b8b498241f8bce263afeae77aaaf9932452cb495e21f09602e93f88b111021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c075e521a840de6ff6daf7c33816a00f70cd82b384775d2de93e2a6c0048ef4c 0.600000000000 1585467 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": 1107806, "vin": [ { "gen": { "height": 1107796 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c075e521a840de6ff6daf7c33816a00f70cd82b384775d2de93e2a6c0048ef4c" } } ], "extra": [ 1, 213, 2, 75, 139, 73, 130, 65, 248, 188, 226, 99, 175, 234, 231, 122, 170, 249, 147, 36, 82, 203, 73, 94, 33, 240, 150, 2, 233, 63, 136, 177, 17, 2, 17, 0, 0, 0, 5, 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