Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 201529fb88e50c640953f5d43c2c744b14238c36367e21035710883f5e5ef4a3

Tx prefix hash: 680a1e54665b065b49b64cbdb3fb8009d711ebb76726a7887c9e497ac126805c
Tx public key: 684426a93e6fe74013b6f48f8ee5edcb664cdba17b0ab16f880e38dc59f6e3fd
Timestamp: 1730037974 Timestamp [UCT]: 2024-10-27 14:06:14 Age [y:d:h:m:s]: 00:028:07:48:49
Block: 1140733 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20231 RingCT/type: yes/0
Extra: 01684426a93e6fe74013b6f48f8ee5edcb664cdba17b0ab16f880e38dc59f6e3fd021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 361ea3e5b17e002b0f5e8f3fa5f8da04f894cd96d3356d6b1921ba589b99fdae 0.600000000000 1624536 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": 1140743, "vin": [ { "gen": { "height": 1140733 } } ], "vout": [ { "amount": 600000000, "target": { "key": "361ea3e5b17e002b0f5e8f3fa5f8da04f894cd96d3356d6b1921ba589b99fdae" } } ], "extra": [ 1, 104, 68, 38, 169, 62, 111, 231, 64, 19, 182, 244, 143, 142, 229, 237, 203, 102, 76, 219, 161, 123, 10, 177, 111, 136, 14, 56, 220, 89, 246, 227, 253, 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