Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4cf8465cb27b64de7eacc9df7dbbee9d4b59c6c17c459c66489d2c8491997601

Tx prefix hash: 635dab9263af0f94ddc180cf7b3904d9e2aeb25deb53a0d7ebd733d93e76cdd5
Tx public key: 769245803f8f0bc0e022bffebdbde873e280ed69a3a44100474b0232f0aa0fba
Timestamp: 1729203941 Timestamp [UCT]: 2024-10-17 22:25:41 Age [y:d:h:m:s]: 00:000:17:00:54
Block: 1133859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 508 RingCT/type: yes/0
Extra: 01769245803f8f0bc0e022bffebdbde873e280ed69a3a44100474b0232f0aa0fba02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4689a97d80c64e2a3a487ed6fc5b2afd1518b679bc1649e1d3733fe569b9b7bc 0.600000000000 1617068 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": 1133869, "vin": [ { "gen": { "height": 1133859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4689a97d80c64e2a3a487ed6fc5b2afd1518b679bc1649e1d3733fe569b9b7bc" } } ], "extra": [ 1, 118, 146, 69, 128, 63, 143, 11, 192, 224, 34, 191, 254, 189, 189, 232, 115, 226, 128, 237, 105, 163, 164, 65, 0, 71, 75, 2, 50, 240, 170, 15, 186, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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