Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c714ca13e4c67cbf95e6356c2035cfb2013a2e53c74c85afc0aabb6ea2d8f1b9

Tx prefix hash: 7512ed65fdb9260b67581ea5f26e1bb727c59092876cdf2f76bdd912530dd2b1
Tx public key: b233e92396ad910f81cb03379fd6fe5f2ce11ce43737e4b3c05bb2429363a692
Timestamp: 1731018051 Timestamp [UCT]: 2024-11-07 22:20:51 Age [y:d:h:m:s]: 00:016:17:17:54
Block: 1148815 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11976 RingCT/type: yes/0
Extra: 01b233e92396ad910f81cb03379fd6fe5f2ce11ce43737e4b3c05bb2429363a692021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d85358960d8f6f3933f4f76c2ad674dd03c98be6e92c6191dfae9e698d59b7fa 0.600000000000 1633746 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": 1148825, "vin": [ { "gen": { "height": 1148815 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d85358960d8f6f3933f4f76c2ad674dd03c98be6e92c6191dfae9e698d59b7fa" } } ], "extra": [ 1, 178, 51, 233, 35, 150, 173, 145, 15, 129, 203, 3, 55, 159, 214, 254, 95, 44, 225, 28, 228, 55, 55, 228, 179, 192, 91, 178, 66, 147, 99, 166, 146, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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